PhysID Documentation
Verifiable identity for physical AI — humanoids, robots, AI glasses. Encode identity into a unit, decode it over NFC or BLE, resolve who's accountable without exposing private data.
Quick start
- Request a sandbox key
- Call
POST https://api.physid.ai/v1/encodewith your operator and unit details - Or point any MCP-compatible client at
https://mcp.physid.ai/mcp
What's in v1
v1 is a sandbox surface. Every API and MCP response carries "mode": "sandbox" so callers cannot mistake stub data for real registry state. The real backend — Concordium agent registry calls, vault-backed key custody, on-chain transfer/revoke — lands in v2.
Endpoints
https://api.physid.ai/v1— REST APIhttps://mcp.physid.ai/mcp— MCP server (JSON-RPC over HTTP, protocol 2025-06-18)
Where to go next
- API overview
- MCP server setup
- Threat model — read before any pilot conversation
- About PhysID — lineage to Provenance Tags + Concordium