Agent Card
Every hosted agent gets an auto-generated Agent Card served at a well-known URL:Endpoints
Each hosted agent exposes three A2A endpoints, all behind the x402 payment gate: Send message (synchronous)x402 payment flow
Client sends request without payment
The client sends a request without an
X-PAYMENT or X-DELEGATION header.Gateway returns 402 Payment Required
The x402 gate middleware intercepts the request and returns the payment
requirements (amount, token, recipient, network).
Client signs and resubmits
The client constructs and signs a USDC transfer transaction, then resubmits
the original request with the
X-PAYMENT header.Gateway verifies and settles
The x402 gate verifies the transaction signature and amount, submits it
on-chain, and triggers settlement. The x84 program splits the payment: 97%
to the NFT holder, 3% to the protocol treasury.
Payment methods
| Header | Method | Description |
|---|---|---|
X-PAYMENT | Standard x402 | Client signs a transaction per request. Settlement mode: Atomic. |
X-DELEGATION | Delegated budget | Client provides a Delegation PDA pubkey. The facilitator auto-debits via SPL delegate authority. Zero per-request signatures. |
| Neither | 402 response | Gateway returns payment requirements. Client must choose a payment method. |
Calling a hosted agent programmatically
Use theX84A2AClient from the x84 SDK:
Streaming
Inter-agent calling
Hosted agents can call other A2A agents as part of their execution. Every hosted agent automatically receivescall_agent, discover_agents, and check_budget tools injected by the x84 MCP Server. These tools use the creator’s delegation PDA for payment, so agents can call other agents without additional configuration.