An agent's name can be copied and its endpoint can change. Credia Identity gives each agent a permanent ID and a public agent card that shows who runs it, what it is for and how to reach or pay it, readable by people and by other software.
Available to selected teams. Request access to discuss your integration.
Credia Identity
Status: Private Beta
Establish an agent's identity and its connection to an operator.
You build or run AI agents and want buyers, platforms and other agents to know who operates them.
Start with Credia Proof-of-Actor to see who or what is using it, and Credia Verify to check an agent's claims before you trust it.
When a person meets a business online, they can check its name, address and website. When they meet an AI agent, there is usually nothing to check: just a name that anyone could copy and an endpoint that may change tomorrow.
Credia Identity gives every agent a permanent ID and a public agent card: who operates it, what it is for, how to contact it, how to pay it, and which claims about it have been checked. The card is a web page for people and structured data for software.
Create the agent in your workspace. It gets a permanent agent ID straight away.
Add the operator, purpose, contact and wallet, and choose which fields are public.
Link Credia Verify checks, such as domain or GitHub ownership, so the card shows what has been confirmed.
Share the card link, or let platforms and other agents look it up by ID.
Situations where knowing which agent you are dealing with matters.
An agent offers to do a job for you. Before you pay, you want to know who is behind it.
How it works
You pay an agent with a known operator, not an anonymous name.
An agent calls your platform or lists itself in your marketplace. You need to know what it is before you trust it.
How it works
Your platform makes consistent decisions about agents, without asking every operator to fill in a form.
You rename your agent, move it to a new endpoint or switch its wallet. Links, history and trust built up so far should not be lost.
How it works
Your agent keeps its track record through every change.
Your company runs dozens of agents for different teams and clients. Nobody is sure which agent belongs to whom.
How it works
One place to see every agent you run and who is responsible for it.
The same lookup for a person in a browser or a program calling the API.
From your website, a payment page, a marketplace listing or a request header.
As a web page, or as structured data for software.
Each field is marked as declared by you or confirmed by a check.
Pay, list, accept the request or ask for more. The decision is always theirs.
An illustrative example of the structured data behind an agent card. The exact beta contract is shared with teams during onboarding.
{
"agentId": "agt_7Hq2k9",
"name": "Research Bot",
"purpose": "Writes market research reports on request",
"operator": { "name": "Acme Labs", "declared": true },
"contact": "[email protected]",
"wallet": { "network": "base", "address": "0x4f3...a91" },
"checks": [
{ "type": "domain", "value": "acme.example", "status": "passed", "checkedAt": "2026-11-02" }
],
"status": "active"
}Credia Identity builds on the public agent pages that come with Credia Payments today. Existing pages keep working at their current addresses, and their history carries over to the agent's permanent ID.
It is not a government ID, a KYC service or a universal registry of every agent on the internet. A field on an agent card is only as reliable as the check behind it, which is why checked fields are labelled individually and unchecked fields are shown as declared by the operator.
Optional publishing of an agent's identity to open registries such as ERC-8004, and publishing the agent's signing keys for Credia Auth, so the same identity works across more of the ecosystem. These are roadmap items, not part of the current beta.
No. A wallet address is one attribute of an agent. The agent ID stays the same even if the wallet, name or endpoint changes.
No. Fields checked by Credia Verify are labelled with the check behind them. Everything else is shown as declared by the operator.
Yes. You choose which fields are public. Private fields stay visible only to your workspace.
Yes. Every agent card is available as structured data, so platforms and other agents can look it up the same way people read the page.
Credia Identity is in Private Beta. Request access to discuss your integration.
Define how an agent authenticates and what authority it can use.
Explore AuthInspect specific claims and the evidence behind them.
Explore VerifyUnderstand activity and outcomes in context over time.
Explore ReputationPayment workflows and controls for AI agents.
Explore PaymentsSee if the traffic in your app is human, AI-assisted or agent traffic.
Explore Proof-of-ActorTell us how many agents you run and who needs to look them up.