Abstraxn
01What it is
Agentic layers / identity layer

Who is this agent?Prove it on chain.

Give each agent a durable, verifiable EVM identity. One prepare/confirm flow registers on an ERC-8004 Identity Registry, mints a chain-native token, and publishes a standard registration file anyone can resolve.

Talk to expert

ERC-8004

open standard

EIP

7 chains

EVM networks supported

non-custodial

owner signs, not Abstraxn

OFF-CHAINON-CHAINREST · agentpreparesign · walletconfirmIdentity Registryregister(agentURI)token ID · ownereip155:…:registry:agentId/agent/…/registrationSTANDARD · ERC-8004PUBLIC agentURI
02Features
Why it matters
05
Portable reputation.
On-chain registration creates a public anchor for reputation, attestations, and future standards built on ERC-8004.
Discoverable agents.
Public registration JSON describes name, description, active status, x402 support, MCP endpoint, and registry bindings.
Verifiable ownership.
Registration is tied to the agent's EVM wallet; confirm verifies the transaction and on-chain owner before persisting identity.
Multi-chain presence.
Register the same logical agent on more than one network. One registration per chain, each with its own token ID and global ID.
Off-chain to on-chain bridge.
Your REST/MCP agent record and your ERC-8004 identity stay linked via agentURI — one product surface, two levels of assurance.

From tenant record to global ID the ecosystem can verify.

03Flow
Up in four steps
  1. 01

    Create and bind the agent

    Provision with POST /agents and bind an EVM wallet address. The registering wallet owner signs the on-chain transaction — Abstraxn never holds keys.

  2. 02

    Prepare registration

    POST /agents/:id/identity/prepare with the target chain. The API returns an unsigned register(agentURI) transaction ready for wallet signing.

  3. 03

    Sign and broadcast

    The agent owner signs and submits to the network. Same non-custodial model as unsigned transfers through the Agent Interface.

  4. 04

    Confirm and persist

    POST /agents/:id/identity/confirm with chain and txHash. On-chain ownership is verified and the global ID is stored. GET /agents/:id/identity returns the full record.

04Published
What gets published

/agent/ endpoints are public (no API key). /agents/ endpoints require your tenant API key.

Public · no API key

GET /agent/{agentId}/registration

EIP-8004 registration-v1 JSON. This URL is written on chain as agentURI, so registries, explorers, and third parties resolve the same document.

  • type — EIP-8004 registration-v1 URI
  • name, description — From the agent record
  • services — MCP endpoint at your kit /mcp (version 2025-06-18)
  • registrations — On-chain bindings: agentId + agentRegistry per chain
  • x402Support — Signals payment-ready agent
  • active — Reflects agent isActive flag

Authenticated read

GET /agents/:id/identity

?chain=sepolia (optional)

Persisted registration state per chain after confirm:

  • chain, chainId, registryAddress
  • agentId (registry token ID)
  • agentIdentity / globalId (eip155:chainId:registry:agentId)
  • agentURI, txHash, owner, registeredAt
05Integrate
For developers

Prerequisites: agent with evmAddress bound, IDENTITY_REGISTRY_{CHAIN} and RPC configured, AGENT_KIT_PUBLIC_URL set for agentURI.

POST /agents/:id/identity/prepare
{
  "chain": "sepolia"
}

// Response: unsignedTransaction, agentURI
  • Public registration URL: https://agent-kit.abstraxn.com/agent/<agentId>/registration
  • Global ID after confirm: eip155:11155111:0x8004…:1

Supported networks

testnettestnettestnet

Where this fits

Explore all agentic layers →
06FAQ
Common questions
Is identity required to use MCP tools?

No. Agents use the Agent Interface without on-chain registration. Identity is for verifiable, discoverable presence when you need it.

Can I register on Solana?

ERC-8004 identity is EVM-only. Bind an EVM address to register; Solana wallets can still be used for Solana MCP tools separately.

Who pays gas for registration?

The wallet that signs the register(agentURI) transaction — typically the agent's bound evmAddress owner.

Can I register the same agent on multiple chains?

Yes — once per supported chain. Each chain gets its own registry token ID and global ID; all appear in the public registration file.

What if someone fetches the registration file before I confirm on chain?

They see the off-chain profile and MCP endpoint. On-chain registrations appear in the JSON only after you complete confirm for each chain.

07Start

One prepare/confirm flow. A public registration file. A global ID partners can trust.

Identity is optional — agents run MCP tools without it. Add it when you need verifiable, discoverable presence across the ecosystem.

Register your first agentERC-8004 identity docs