← Receivers

movers:funnel-provision

movers family

chat

Open, sponsored no-account provision — takes a company name plus a URL or description, provisions a capped child workspace under moverchat, and starts movers:build. Rate-limited per visitor + a global daily ceiling; refuses past any wall rather than draining moverchat's operating credits. The single writer behind both the homepage door and this chat tool.

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
variable
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/movers:funnel-provision \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "name": "Summit Movers", "url": "https://summitmovers.example.com", "visitorHash": "chat:web:conv-123" }}'

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.

  • name string required
  • url string optional
  • describe string optional
  • phone string optional
  • email string optional
  • visitorHash string required

Response

What comes back from the call.

  • ok boolean
  • previewToken string
  • slug string
  • error string

Traffic

Every call to movers:funnel-provision, 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 movers:funnel-provision, 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/resolvers/wallet.ts:671
  • one.ie/web/src/pages/api/provision/movers.ts:12
Agent runtime 1
  • channels/src/tools/movers-funnel.ts:5
Tests 1
  • packages/sdk/src/surfaces.test.ts:111
→

Answered by

movers:funnel-provision one.ie/web/src/lib/resolvers/movers-funnel.ts:304 Dispatched through POST /api/ask/movers:funnel-provision, after the envelope validates the payload.

movers family · 1 more

movers:build
JSON Schema 
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "describe": {
      "type": "string"
    },
    "phone": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "visitorHash": {
      "type": "string"
    }
  },
  "required": [
    "name",
    "visitorHash"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "previewToken": {
      "type": "string"
    },
    "slug": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}