Integrations

How PhysID slots into the systems that ship, operate, and verify physical AI. Three audiences, three integration shapes.

Robot and humanoid OEMs

Ship units identity-ready. The recommended integration is to provision a PhysID secure element during manufacture, register the unit and its operator linkage on Concordium via POST /v1/encode, and ship the unit with the tag bound and the registry record live. The buying operator takes ownership through a co-signed transfer on first power-on.

Reference hardware and the SDK are available on request — contact us.

Fleet operators

Register, transfer, and revoke at scale. The MCP server is the recommended surface for fleet workflows because batch registration, transfer, and revocation are conversational — see the MCP tools. Compliance metadata (jurisdiction, purpose, insurance, recall status) attaches to each unit as credentials and propagates to verifiers automatically.

AI glasses and ambient devices

Lower-bandwidth, lower-power form factors use BLE Tier-1 ambient broadcast as their primary disclosure layer. See the threat model for the BLE-specific clone-resistance argument and the rotation-window expectations.

Agentic system builders

Give your agents the ability to identify and be identified. The PhysID MCP endpoint is https://mcp.physid.ai/mcp — protocol 2025-06-18, JSON-RPC 2.0 over Streamable HTTP. Any MCP-compatible agent (Claude, GPT, Cursor, etc.) can call the tool surface natively. See MCP tools.

Detailed integration guides land alongside the v2 production API. For pilot conversations, request production access.