agent:provision

Zero-to-live in one unauthenticated call — register + workspace + publish agent + import skills + invite owner

Effect: ask; Awaits an outcome — the call returns the response below.
Caller: none; The class of authority the caller must already hold, decided from the attested context with no round trip.
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/agent:provision \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "name": <string>, "agentName": <string>, "content": <string>, "skills": <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.

name string optional
agentName string optional
content string optional
skills string[] optional
invite object optional
live boolean optional

Response

What comes back from the call.

uid string
workspace string
apiKey string
inviteUrl string

Traffic

Every call to agent: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 agent: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 1

one.ie/web/src/lib/step-ceiling.ts:91

→

Answered by

agent:provision Resolved outside this repo — the pay, channels or api worker answers it. Dispatched through POST /api/ask/agent:provision, after the envelope validates the payload.

agent family · 4 more

agent:bootstrap agent:enroll agent:own-link agent:run

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "agentName": {
      "type": "string"
    },
    "content": {
      "type": "string"
    },
    "skills": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "invite": {
      "type": "object",
      "properties": {
        "email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
        },
        "role": {
          "type": "string"
        }
      }
    },
    "live": {
      "type": "boolean"
    }
  }
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "uid": {
      "type": "string"
    },
    "workspace": {
      "type": "string"
    },
    "apiKey": {
      "type": "string"
    },
    "inviteUrl": {
      "type": "string"
    }
  },
  "required": [
    "uid",
    "workspace",
    "apiKey"
  ]
}