← Receivers

world:in

world family

The one front door: a message enters the world inbox, a guard quarantines toxic content, the router classifies the destination (private/fanout/public), and delivers into each destined workspace. Delivery is opt-in (a workspace receives only tags it subscribed) with one exception: a caller may always direct to a workspace it owns. A directed message that can't be delivered fails closed (ok:false) — it never falls back to the public feed.

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
session
The class of authority the caller must already hold, decided from the attested context with no round trip.
Reversible
no
This cannot be undone. Dry-run it first where the contract allows.

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/world:in \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "content": <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.

  • content string required
  • tags string[] optional
  • to string optional
  • from string optional

Response

What comes back from the call.

  • ok boolean
  • decision private | fanout | public | quarantine
  • targets string[]
  • delivered string[]
  • guard object
  • note string
  • error string

Traffic

Every call to world:in, 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 world:in, 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 3
  • one.ie/web/src/lib/ingress.ts:3
  • one.ie/web/src/lib/world-receivers.ts:2159
  • one.ie/web/src/pages/api/receivers/signals.ts:11
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "content": {
      "type": "string",
      "minLength": 1
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "to": {
      "type": "string"
    },
    "from": {
      "type": "string"
    }
  },
  "required": [
    "content"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "decision": {
      "type": "string",
      "enum": [
        "private",
        "fanout",
        "public",
        "quarantine"
      ]
    },
    "targets": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "delivered": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "guard": {
      "type": "object",
      "properties": {
        "toxic": {
          "type": "boolean"
        },
        "score": {
          "type": "number"
        },
        "reason": {
          "type": "string"
        }
      },
      "required": [
        "toxic",
        "score",
        "reason"
      ]
    },
    "note": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}