ONE ramp:status
← Receivers

ramp:status

ramp family

chatmcp

What is true about adding money and cashing out today: whether each door is open, every reason it is not (countries, ID check, bank or payout partner), what comes next, and what works today. The same facts as one.ie/on and one.ie/off. No provider is named as live. Anyone may ask; nothing personal is returned.

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
public
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
yes
The effect can be undone by a later call.
Idempotent
yes
Safe to retry as-is.
Version
1.0.0
Pin this to keep a contract stable; additive bumps never break callers.

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/ramp:status \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": {}}'

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.

Takes no arguments.

Response

What comes back from the call.

  • ok boolean
  • network string This deploy's network word for USDC, e.g. 'Sui' or 'Sui testnet'
  • on any Add money: { door, title, open, pill, why, stops, checks: [{ key, ok, label, state, detail, clause }], next, today, one, summary }
  • off any Cash out: the same shape
  • error string

Traffic

Every call to ramp:status, 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 ramp:status, 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 2
  • one.ie/web/src/lib/receiver-index.generated.ts:343
  • one.ie/web/src/lib/resolvers/ramp.ts:78
CLI 2
  • packages/cli/src/lib/money-receivers.ts:29
  • packages/cli/src/ramp.ts:43
Tests 1
  • packages/sdk/src/surfaces.test.ts:139
→

Answered by

ramp:status one.ie/web/src/lib/resolvers/ramp.ts:76 Dispatched through POST /api/ask/ramp:status, after the envelope validates the payload.

ramp family · 3 more

JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {}
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "network": {
      "description": "This deploy's network word for USDC, e.g. 'Sui' or 'Sui testnet'",
      "type": "string"
    },
    "on": {
      "description": "Add money: { door, title, open, pill, why, stops, checks: [{ key, ok, label, state, detail, clause }], next, today, one, summary }"
    },
    "off": {
      "description": "Cash out: the same shape"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}