← Receivers

news:ingest

news family

Fetch the feeds that are due — once each, for every group that follows them. Conditional GET, size and time caps, every URL and redirect hop through the SSRF guard. Run by the platform clock; not a per-group call

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
platform
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
no
This cannot be undone. Dry-run it first where the contract allows.
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:ingest \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "limit": <number> }}'

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.

  • limit number optional

Response

What comes back from the call.

  • ok boolean
  • feeds_due number
  • fetched number
  • not_modified number
  • failed number
  • items_new number
  • truncated number Feeds larger than the 1 MB read cap: read from their head (newest items), not refused.
  • capped boolean True when more feeds were due than this tick would fetch.
  • refused object
  • error string

Traffic

Every call to news:ingest, 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:ingest, 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:238
Agent runtime 1
  • channels/src/cron.ts:53
→

Answered by

news:ingest one.ie/web/src/lib/resolvers/news.ts:191 Dispatched through POST /api/ask/news:ingest, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    }
  }
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "feeds_due": {
      "type": "number"
    },
    "fetched": {
      "type": "number"
    },
    "not_modified": {
      "type": "number"
    },
    "failed": {
      "type": "number"
    },
    "items_new": {
      "type": "number"
    },
    "truncated": {
      "description": "Feeds larger than the 1 MB read cap: read from their head (newest items), not refused.",
      "type": "number"
    },
    "capped": {
      "description": "True when more feeds were due than this tick would fetch.",
      "type": "boolean"
    },
    "refused": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {
        "type": "number"
      }
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}