billing:plan

Change a workspace's plan — returns a checkout URL to complete the upgrade

Effect: ask; Awaits an outcome — the call returns the response below.
Caller: update_group; 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/billing:plan \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "slug": <string>, "actorId": <string>, "plan": <pro | agency | scale> }}'

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
actorId string required
plan pro | agency | scale required

Response

What comes back from the call.

ok boolean
intent string
checkoutUrl string
plan string
reason string

Traffic

Every call to billing:plan, 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 billing:plan, 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/resolvers/market.ts:1578

Agent runtime 1

channels/src/tools/billing.ts:6

Workflow 1

one.ie/web/src/lib/workflow-templates.ts:967

→

Answered by

billing:plan one.ie/web/src/lib/resolvers/market.ts:1577 Dispatched through POST /api/ask/billing:plan, after the envelope validates the payload.

billing family · 3 more

billing:clients billing:set-markup billing:topup

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "slug": {
      "type": "string"
    },
    "actorId": {
      "type": "string"
    },
    "plan": {
      "type": "string",
      "enum": [
        "pro",
        "agency",
        "scale"
      ]
    }
  },
  "required": [
    "slug",
    "actorId",
    "plan"
  ]
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "intent": {
      "type": "string"
    },
    "checkoutUrl": {
      "type": "string"
    },
    "plan": {
      "type": "string"
    },
    "reason": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}