For developers: five minutes in

Test it with your own agent

Start the project locally, then give this prompt to an agent that can call MCP. It exercises the development interface and reports the exact responses. TapeID has no public MCP endpoint, deployed contracts or chain transactions yet.

Exercise the TapeID interface only in a local development environment.
Read https://tapeid.xyz/ask.txt if available. Start the project locally and use http://127.0.0.1:3002/mcp.
Do not report an on-chain registration or transaction: TapeID is not deployed.
Return exact local responses and clearly label every result as a development test.

Read something locally

curl "http://127.0.0.1:3001/v1/names/atlas/available"

curl "http://127.0.0.1:3001/v1/names/atlas"

Every response is one envelope: summary (the answer in a sentence), data, errors, and meta with the chain it came from. Full list in the REST reference.

Exercise registration with local MCP

Start the local services, then point your MCP client at http://127.0.0.1:3002/mcp. The reserved public path https://tapeid.xyz/mcp is not live.

{
  "mcpServers": {
    "tapeid": { "type": "http", "url": "http://127.0.0.1:3002/mcp" }
  }
}

The development flow, using only a local chain and disposable wallets:

check_name            → local policy and availability response
prepare_registration  → an EIP-712 payload to sign
submit_registration   → a local test mint, never a public registration
prepare_card          → the card payload to sign (personal_sign)
submit_card           → a local development write

An agent without a wallet can test request_name → owner confirmation (valid for 15 minutes) → get_status. TapeID has no registered users or inherited agent success stories.

Without MCP: plain HTTP

curl -X POST "http://127.0.0.1:3001/v1/requests" \
  -H 'content-type: application/json' \
  -d '{"label":"atlas","requestedFor":"0xYourWallet","host":"your-agent"}'

What to know before you build

• Writes need a wallet signature — EIP-712 for registration, personal_sign for cards. There is no server-side key that can spend anything of yours.
• Rate limits and quotas are configuration and are published: https://tapeid.xyz/v1/metrics.
• If your agent holds no key but you run a signer for it, the agent signer keeps the key out of the agent.