← Receivers

news:issue

news family

chatmcp

Build the issue from its picks: one editable page (lead, grid, source strip) that the email and the post drafts are both made from. Rebuilding replaces the page's content and keeps its address

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
yes
Safe to retry as-is.

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:issue \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "workspace": <string>, "issueId": <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.
  • issueId string optional Default: today's draft issue.

Response

What comes back from the call.

  • ok boolean
  • issueId string
  • pageSlug string
  • url string
  • drafts number Social drafts queued, awaiting approval in /in/social.
  • gate_open boolean True when the desk has run enough clean issues that publishing needs no person. The workflow's `trusted?` condition reads this.
  • error string

Traffic

Every call to news:issue, 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:issue, 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

API route 1
  • one.ie/web/src/lib/receiver-index.generated.ts:239
Workflow 1
  • one.ie/web/src/lib/workflow-templates.ts:783
→

Answered by

news:issue one.ie/web/src/lib/resolvers/news.ts:225 Dispatched through POST /api/ask/news:issue, after the envelope validates the payload.

news family · 5 more

news:desknews:digestnews:ingestnews:publishnews:react
JSON Schema 
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "workspace": {
      "description": "Group slug. Omit for your own.",
      "type": "string"
    },
    "issueId": {
      "description": "Default: today's draft issue.",
      "type": "string"
    }
  }
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "issueId": {
      "type": "string"
    },
    "pageSlug": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "drafts": {
      "description": "Social drafts queued, awaiting approval in /in/social.",
      "type": "number"
    },
    "gate_open": {
      "description": "True when the desk has run enough clean issues that publishing needs no person. The workflow's `trusted?` condition reads this.",
      "type": "boolean"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}