auth:agent

auth family

Become an actor — mint a uid and a scoped API key, and register an empty wallets row; addresses are registered afterwards by wallet:challenge proof

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.
Reversible: no; This cannot be undone. Dry-run it first where the contract allows.
Idempotent: yes; Safe to retry as-is.

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/auth:agent \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "name": <string>, "uid": <string>, "kind": <string>, "wallet": <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
uid string optional
kind string optional
wallet string optional

Response

What comes back from the call.

uid string
name string
kind string
wallet string | null
apiKey string
keyId string
returning boolean

Traffic

Every call to auth:agent, 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 auth:agent, 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 3

one.ie/web/src/lib/act-as.ts:196
one.ie/web/src/lib/receiver-index.generated.ts:48
one.ie/web/src/pages/api/auth/agent.ts:133

Docs 2

one.ie/web/src/content/docs/mcp.md:183
one.ie/web/src/content/docs/sdk.md:241

→

Answered by

auth:agent one.ie/web/src/lib/resolvers/auth.ts:69 Dispatched through POST /api/ask/auth:agent, after the envelope validates the payload.

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "uid": {
      "type": "string"
    },
    "kind": {
      "type": "string"
    },
    "wallet": {
      "type": "string"
    }
  }
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "uid": {
      "type": "string"
    },
    "name": {
      "type": "string"
    },
    "kind": {
      "type": "string"
    },
    "wallet": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    },
    "apiKey": {
      "type": "string"
    },
    "keyId": {
      "type": "string"
    },
    "returning": {
      "type": "boolean"
    }
  },
  "required": [
    "uid",
    "name",
    "kind",
    "wallet",
    "apiKey",
    "keyId",
    "returning"
  ]
}