← Receivers

identity:verify

identity family

Start a verification method for an address and get back a single-use challenge plus the fresh random salt to commit with. Takes no identifier and returns none: the caller proves the contact point to the issuer out of band, and only the salted commitment ever travels.

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
session
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.

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/identity:verify \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "subject": <string>, "method": <passkey | google | phone | …> }}'

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.

  • subject string required the Sui address being verified — public, never a person
  • method passkey | google | phone | … required which rung is being attempted; `key` needs no challenge and `owner-of` is issued by the spawns walk, so neither is startable here

Response

What comes back from the call.

  • ok boolean
  • challenge string single-use nonce; the attestation that spends it can never be replayed
  • salt string 32 fresh random bytes as hex, for the holder to KEEP — it is what lets them open the commitment later, to one counterparty, off chain
  • method string
  • level number the rung this method would confer: 0 key · 1 passkey · 2 google/phone · 3 domain · 4 kyc
  • expiresAt number
  • error string a refusal CODE — never quotes an identifier, a salt or a key

Traffic

Every call to identity:verify, 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 identity:verify, 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/identity/verification.ts:239

Answered by

identity:verify Resolved outside this repo — the pay, channels or api worker answers it. Dispatched through POST /api/ask/identity:verify, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "subject": {
      "type": "string",
      "minLength": 1,
      "description": "the Sui address being verified — public, never a person"
    },
    "method": {
      "type": "string",
      "enum": [
        "passkey",
        "google",
        "phone",
        "domain",
        "kyc"
      ],
      "description": "which rung is being attempted; `key` needs no challenge and `owner-of` is issued by the spawns walk, so neither is startable here"
    }
  },
  "required": [
    "subject",
    "method"
  ],
  "additionalProperties": false
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "challenge": {
      "description": "single-use nonce; the attestation that spends it can never be replayed",
      "type": "string"
    },
    "salt": {
      "description": "32 fresh random bytes as hex, for the holder to KEEP — it is what lets them open the commitment later, to one counterparty, off chain",
      "type": "string"
    },
    "method": {
      "type": "string"
    },
    "level": {
      "description": "the rung this method would confer: 0 key · 1 passkey · 2 google/phone · 3 domain · 4 kyc",
      "type": "number"
    },
    "expiresAt": {
      "type": "number"
    },
    "error": {
      "description": "a refusal CODE — never quotes an identifier, a salt or a key",
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}