On-chain AI agent identity, authenticity, and risk verification via the ERC-8004 standard.
What it does
The Cybercentry ERC-8004 Agent Verification (CEAV) API provides on-chain verification of AI agents using the ERC-8004 standard. Given an agent identifier, it returns verification results covering identity, authenticity, and risk assessment. The endpoint is x402-enabled, settling payments in USDC on Base network at $0.10 per call.
The API accepts a POST request with an `agentId` query parameter — the unique identifier of the AI agent to verify — and returns a JSON object containing a `verification` object with the results. The landing page also documents the endpoint as accessible via GET. The x402 challenge confirms the endpoint is live and requires an `X-PAYMENT` header for payment settlement.
Documentation beyond the landing page is not available (no OpenAPI spec, no /docs, no /api routes). The output schema in the x402 challenge describes the verification response as a generic object without detailed field definitions, so the exact structure of the verification payload is unknown. The service is hosted on Railway and settles to address 0xfEE13309251B632317ea2d475d6ABa7E7E0219e6 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base.
Capabilities
Use cases
- —Verify the identity and authenticity of an AI agent before interacting with it
- —Assess the risk profile of an AI agent registered under the ERC-8004 standard
- —Integrate on-chain agent verification into multi-agent orchestration pipelines
- —Gate access to sensitive resources based on verified agent identity
Fit
Best for
- —Developers building multi-agent systems that need trust verification
- —Platforms that need to authenticate AI agents before granting access
- —On-chain identity checks for ERC-8004-registered agents
Not for
- —Verifying human user identities or traditional OAuth/SSO flows
- —Agents not registered under the ERC-8004 standard
Quick start
curl -X POST "https://x402-cybercentry-erc-8004-agent-verification.up.railway.app/verify?agentId=YOUR_AGENT_ID" \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Example
Request
{
"url": "https://x402-cybercentry-erc-8004-agent-verification.up.railway.app/verify?agentId=0x1234abcd5678ef90",
"method": "POST",
"headers": {
"X-PAYMENT": "<x402_payment_token>",
"Content-Type": "application/json"
}
}Response
{
"verification": {
"risk": {},
"status": "verified",
"agentId": "0x1234abcd5678ef90",
"identity": {}
}
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear x402 payment scheme and basic input schema, but there is no OpenAPI spec, no detailed output schema, and no documentation beyond the landing page. The response structure of the verification object is entirely unknown and the example response is speculative.
Warnings
- —No OpenAPI or detailed API documentation available
- —Output schema for the verification object is unspecified — response fields are inferred
- —Landing page says GET /verify but x402 challenge was captured on POST — actual supported method(s) unclear
- —Example response JSON is speculative; actual field names and structure are unknown
Citations
- —The endpoint costs $0.10 per call in USDC on Base (maxAmountRequired 100000 with 6 decimals = $0.10)https://x402-cybercentry-erc-8004-agent-verification.up.railway.app
- —Landing page describes the service as ERC-8004 Agent Verification with micropayment-based access controlhttps://x402-cybercentry-erc-8004-agent-verification.up.railway.app
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://x402-cybercentry-erc-8004-agent-verification.up.railway.app
- —Payment recipient address: 0xfEE13309251B632317ea2d475d6ABa7E7E0219e6https://x402-cybercentry-erc-8004-agent-verification.up.railway.app