Agents have identity.
They deserve credentials too.
ERC-8004 solved onchain identity for agents. iAgentID will solve credentials. Proof an agent completed this course, is authorized by this operator, passed these benchmarks, achieved this iAgentFi rating. W3C Verifiable Credentials for the agent economy. Cluster 3 roadmap 2028.
iAgentID will provide four primitives
Credential issuance
Any iJarvis-registered issuer can mint signed credentials. iAgentFi issues rating credentials. iAgentSim issues safety-benchmark credentials. Operators issue authorization credentials.
Cross-chain identity
DID-based agent identity that resolves consistently across Ethereum, Base, Avalanche, BNB, and non-blockchain contexts.
Credential verification
Fast, cached verification API. Agents can gate actions on counterparty credentials without building signature logic.
Revocation & expiry
First-class support for credential lifecycle. Revoked credentials propagate to cached verifiers within seconds.
The gap iAgentID fills
Identity ≠ credentials
ERC-8004 answers 'who is this agent?' iAgentID answers 'what has this agent proven?' Both are required for real trust.
W3C standards compatible
Built on W3C VC Data Model. Interoperates with existing credential infrastructure from enterprise SSO to academic credentialing.
Composable with the stack
Every other iJarvis product either issues or consumes iAgentID credentials. The common trust substrate.
Planned endpoints in Roadmap 2028 (Cluster 3)
Preview of the planned API surface. OpenAPI 3.1 specification at /.well-known/openapi.yaml. Endpoints at api.iagentid.com will serve requests at roadmap 2028 (cluster 3); agent-consumable JSON by design.
POST /v1/credentials/issue |
Issue a signed credential |
GET /v1/credentials/verify |
Verify a credential's signature + chain |
POST /v1/credentials/revoke |
Revoke a previously issued credential |
GET /v1/agent/{did}/credentials |
Retrieve all credentials for an agent |
GET /v1/issuers |
Registry of verified credential issuers |
iAgentID is one layer
Sixteen products. One stack. One entity. Trust, discovery, observability, payments, safety, simulation, composition, memory, identity, legal, markets, and owned compute underneath. Each layer reinforces the others. Use one or use them all.