← Receivers

news:digest

news family

chatmcp

Pick and rank the day's stories for one group, write each take from the article only, find a picture, and store them as today's draft issue. Returns the issue id and honest counts — fetched · eligible · folded · kept · capped (with the budget that bit) · skipped by reason. Re-running the same day replaces the picks and keeps the issue

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
manage_workspace
The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost
variable
What one call costs, so you can budget before acting.
Reversible
yes
The effect can be undone by a later call.
Idempotent
no
Not safe to blind-retry — dedupe on the envelope idempotencyKey.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code
Codex
Cursor
Gemini CLI
Claude Desktop
ChatGPT
curl -X POST https://one.ie/api/ask/news:digest \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "workspace": <string> }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

  • workspace string optional Group slug. Omit for your own.

Response

What comes back from the call.

  • ok boolean
  • issueId string
  • counts object
  • held string Why the issue is held (e.g. `ungrounded`): a person must fix or drop a story before it can publish.
  • cost_credits number
  • error string

Traffic

Every call to news:digest, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names news:digest, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

UI 1
  • one.ie/web/src/components/news/deskApi.ts:125
API route 2
  • one.ie/web/src/lib/news/digest.ts:43
  • one.ie/web/src/lib/receiver-index.generated.ts:237
Workflow 1
  • one.ie/web/src/lib/workflow-templates.ts:782
→

Answered by

news:digest one.ie/web/src/lib/resolvers/news.ts:200 Dispatched through POST /api/ask/news:digest, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "workspace": {
      "description": "Group slug. Omit for your own.",
      "type": "string"
    }
  }
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "issueId": {
      "type": "string"
    },
    "counts": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "held": {
      "description": "Why the issue is held (e.g. `ungrounded`): a person must fix or drop a story before it can publish.",
      "type": "string"
    },
    "cost_credits": {
      "type": "number"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}