← Receivers

pages:bulk

pages family

Apply ONE op (publish | unpublish | delete) to an EXPLICIT list of pages — one authority walk, one round trip, a per-row answer.

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
member
The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost
free
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/pages:bulk \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "slug": <string>, "op": <publish | unpublish | delete>, "pages": <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.

  • slug string required
  • op publish | unpublish | delete required
  • pages string[] required Page slugs, REQUIRED and non-empty. There is deliberately no omitted-means-all case: pages:publish-pack has one, and an implicit whole-workspace scope is exactly what a selection UI must never be able to send. Over 100 is refused BY NAME (`too_many:N>100`), never truncated.

Response

What comes back from the call.

  • ok boolean Describes THE CALL, not the rows. A run where every row failed still answers ok:true — read `changed` and `failed`, never this, to report what happened.
  • op string
  • requested number Rows attempted, after de-duplication.
  • changed number Rows the op actually changed. This is the number to quote.
  • failed number requested - changed. Present even when 0, so a caller cannot miss it.
  • results object[] Per-row outcome, in the order attempted. A failed row names its own reason (`not_found`, `no_db`).
  • error string

Traffic

Every call to pages:bulk, 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 pages:bulk, 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/pages/PagesGrid.tsx:55
API route 1
  • one.ie/web/src/lib/resolvers/pages.ts:271
→

Answered by

pages:bulk one.ie/web/src/lib/resolvers/pages.ts:937 Dispatched through POST /api/ask/pages:bulk, after the envelope validates the payload.

pages family · 12 more

pages:createpages:deletepages:editpages:fill-packpages:fill-pack-extractpages:listpages:publishpages:publish-packpages:restorepages:unpublishpages:versionspages:view
JSON Schema 
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "slug": {
      "type": "string"
    },
    "op": {
      "type": "string",
      "enum": [
        "publish",
        "unpublish",
        "delete"
      ]
    },
    "pages": {
      "minItems": 1,
      "maxItems": 100,
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Page slugs, REQUIRED and non-empty. There is deliberately no omitted-means-all case: pages:publish-pack has one, and an implicit whole-workspace scope is exactly what a selection UI must never be able to send. Over 100 is refused BY NAME (`too_many:N>100`), never truncated."
    }
  },
  "required": [
    "slug",
    "op",
    "pages"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean",
      "description": "Describes THE CALL, not the rows. A run where every row failed still answers ok:true — read `changed` and `failed`, never this, to report what happened."
    },
    "op": {
      "type": "string"
    },
    "requested": {
      "description": "Rows attempted, after de-duplication.",
      "type": "number"
    },
    "changed": {
      "description": "Rows the op actually changed. This is the number to quote.",
      "type": "number"
    },
    "failed": {
      "description": "requested - changed. Present even when 0, so a caller cannot miss it.",
      "type": "number"
    },
    "results": {
      "description": "Per-row outcome, in the order attempted. A failed row names its own reason (`not_found`, `no_db`).",
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "slug": {
            "type": "string"
          },
          "ok": {
            "type": "boolean"
          },
          "title": {
            "type": "string"
          },
          "error": {
            "type": "string"
          }
        },
        "required": [
          "slug",
          "ok"
        ]
      }
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}