← Receivers

pages:remove-block

pages family

Drop ONE block from a page by id. Every other block is preserved verbatim. NOT undoable through this door — the page's prior state lives only in a pages:versions snapshot if one was taken.

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
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/pages:remove-block \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "slug": <string>, "page": <string>, "blockId": <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 The workspace slug.
  • page string required The page's own slug.
  • blockId string required The block's id, as `pages:get` reports it in `blocks[]`.

Response

What comes back from the call.

  • ok boolean
  • slug string
  • title string
  • url string
  • status string
  • blocks number
  • updatedAt number
  • error string

Traffic

Every call to pages:remove-block, 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:remove-block, 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/live-edit/LiveEditSheet.tsx:86
API route 1
  • one.ie/web/src/lib/receiver-index.generated.ts:227
Agent runtime 1
  • channels/src/tools/pages.ts:349
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The workspace slug."
    },
    "page": {
      "type": "string",
      "description": "The page's own slug."
    },
    "blockId": {
      "type": "string",
      "description": "The block's id, as `pages:get` reports it in `blocks[]`."
    }
  },
  "required": [
    "slug",
    "page",
    "blockId"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "slug": {
      "type": "string"
    },
    "title": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "blocks": {
      "type": "number"
    },
    "updatedAt": {
      "type": "number"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}