Incarna Documentation
Your agent has a mind and a wallet. Incarna gives it a body.
An agent that can reason and pay still cannot be anywhere. It has no inbox that receives, no handle that persists, no device or place it comes from. Incarna is the layer that supplies those — and keeps them consistent, so the identity holds up over time instead of looking new every session.
Base URL https://api.incarna.io
MCP https://api.incarna.io/mcpEvery page here is also served as Markdown at its own URL plus .md, and the whole
set is at llms.txt and llms-full.txt — this is
documentation agents are expected to read directly.
Three ways in
Incarna has one core and three front doors. They are not tiers — they answer different questions about who is calling.
REST, with an API key. A developer builds a product on top of us; their backend holds the key and their users never see it. Start at the Quickstart.
MCP, over HTTP. An agent runtime — an AgentCore Gateway, Claude, Cursor — connects once and the whole capability set appears as tools. Same key, same org, same billing. See MCP.
x402, pay-per-call. No plan, no invoice, no billing set up in advance: the
endpoint answers 402 with signable terms, the caller pays, the action runs. This
is the door for an agent that holds a wallet and settles its own costs. See
x402.
What it is not
Incarna operates identities its customers own or provision. It does not manufacture proof of personhood — no government ID, no biometrics, nothing that asserts a human where there is none. An agent's body is a real, consistent presence on the network; it is not a claim to be a person.