ONE name:get
← Receivers

name:get

name family

mcp

A workspace's current name, its URL, and the names it retired (each still answers with a redirect to the current one). Reads your own workspace, or one you control by `workspace`; a workspace you do not control is refused, never swapped for yours

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
member
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.
Version
1.0.0
Pin this to keep a contract stable; additive bumps never break callers.

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

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.

  • workspace string optional The workspace slug to read; omit for the caller's own

Response

What comes back from the call.

  • ok boolean
  • workspace string The slug, the key that never changes
  • name string | null The current name; null when the workspace answers at its slug
  • url string
  • retired string[]
  • error string

Traffic

Every call to name: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 name: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 2
  • one.ie/web/src/lib/onboard/company-walk.ts:28
  • one.ie/web/src/lib/receiver-index.generated.ts:256
CLI 1
  • packages/cli/src/name.ts:42
→

Answered by

name:get one.ie/web/src/lib/resolvers/names.ts:108 Dispatched through POST /api/ask/name:get, after the envelope validates the payload.

name family · 2 more

JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "workspace": {
      "description": "The workspace slug to read; omit for the caller's own",
      "type": "string"
    }
  }
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "workspace": {
      "description": "The slug, the key that never changes",
      "type": "string"
    },
    "name": {
      "description": "The current name; null when the workspace answers at its slug",
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    },
    "url": {
      "type": "string"
    },
    "retired": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}