← Receivers

wallet:lock-get

wallet family

Public read: the lock a name has published, with everything needed to re-verify it offline (lock, Sui signer, signature, the exact signed text, publishedAt). `published:false` when none, or when the signer is no longer the account's registered Sui address (after wallet:rotate). Also served as GET /api/lock/<slug>, and /api/lock/<slug>/<agent-id> for an agent's own lock

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.

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/wallet:lock-get \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "slug": "tony" }}'

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.

  • slug string required The name (workspace slug) whose lock to look up
  • agent string optional An agent id in that workspace: answers the agent's own lock, never the workspace's person lock

Response

What comes back from the call.

  • ok boolean
  • published boolean
  • lock string
  • suiAddress string
  • signature string
  • message string
  • publishedAt string
  • error string

Traffic

Every call to wallet:lock-get, 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 wallet:lock-get, 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 4
  • one.ie/web/src/lib/api/lock-door.ts:7
  • one.ie/web/src/lib/key/lock-lookup.ts:7
  • one.ie/web/src/lib/receiver-index.generated.ts:412
  • one.ie/web/src/lib/resolvers/wallet.ts:1415
SDK 1
  • packages/sdk/src/message-lock.ts:127
→

Answered by

wallet:lock-get one.ie/web/src/lib/resolvers/wallet.ts:1434 Dispatched through POST /api/ask/wallet:lock-get, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "The name (workspace slug) whose lock to look up"
    },
    "agent": {
      "description": "An agent id in that workspace: answers the agent's own lock, never the workspace's person lock",
      "type": "string"
    }
  },
  "required": [
    "slug"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "published": {
      "type": "boolean"
    },
    "lock": {
      "type": "string"
    },
    "suiAddress": {
      "type": "string"
    },
    "signature": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "publishedAt": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}