Back to Browse
AgentVerify Badge Issuance
x402
AgentVerify Badge Issuance is a paid API for AI agents from agentverify.t-horizon.co.za, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-31).
Issues a signed Ed25519 trust badge (VC+JWT) for a registered agent identity on the AgentVerify network
Price / call$0.02
Success—
StatusUnknown
How this service works
AgentVerify lets autonomous agents prove identity, record commercial dealings, and check each other's trust before they transact. Paid routes use the x402 protocol (HTTP 402, USDC on an EVM network). Set `PAYMENTS_MODE=off` for local development. The server holds a receive-only wallet address and an Ed25519 key used only to sign trust badges.
Output
Returns a compact VC+JWT string (the 'badge'), the agent's subject DID (e.g. 'av:0123…'), the signing algorithm ('EdDSA'), and the token type ('vc+jwt'). This credential can be presented to other agents or services to prove identity and trustworthiness.
Example use cases
Onboarding a new autonomous trading agent
“My new trading agent just came online — can you issue it an AgentVerify trust badge using its agent ID 'av:abc123def456' so it can prove its identity to counterparties before placing any orders?”
Pre-transaction identity proof between agents
“Before my fulfillment agent sends payment to the supplier agent, I need it to present a valid AgentVerify VC+JWT badge — go ahead and issue one for agent ID 'av:9f8e7d6c5b4a3210' so the handshake can complete.”
Credentialing an agent fleet for a marketplace
“I'm deploying five agents to a marketplace that requires each one to carry a signed AgentVerify trust badge — please issue a badge for agent ID 'av:fleet-unit-001' as the first step.”
Technical details
Endpoint
POSThttps://agentverify.t-horizon.co.za/v1/agents/%7Bagent_id%7D/badge?utm_source=zero.xyzWhen to prefer
Choose this endpoint when an autonomous agent needs to obtain a cryptographically signed, portable identity credential (VC+JWT) that can be presented to other agents or services before a commercial transaction. It is the right choice when inter-agent trust, verifiable identity, and EdDSA-signed badges are required — not for simple API key auth or human user login flows.
Side effects
- Missing or invalid agent_id in the path — returns 400 or 404
- Insufficient x402 payment (USDC) — returns HTTP 402 requiring payment
- Malformed request body — returns 400 with validation error
- Agent not registered on the network — returns 404 not found
- Payment network unavailable or EVM node unresponsive — returns 503
- Expired or replayed payment token — returns 402 or 401
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object | |
| description | string |
Output
Schema · Response
{
"type": "json",
"example": {
"badge": "<compact vc+jwt>",
"subject": "av:0123456789abcdef0123456789abcdef",
"algorithm": "EdDSA",
"token_type": "vc+jwt"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"