Services / API · Registry
Exa
POST https://api.exa.ai/contents
Listed in a public agent registry. The name is the registry's label, not ours. Not reviewed by a person. See all 4 endpoints from exa.ai.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✓ its latest check passed; ✓ at least 5 payers in 30 days (registry figure); ✓ listed in a curated catalogue (counts in place of the payer figure).
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:480eip155:5042tempo:4217 | 95 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:480eip155:5042 | 244 ms |
cloudflare:SCL |
Live, valid payment request HTTP 402 | eip155:8453solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpeip155:480eip155:5042 | 197 ms |
What this evidence does not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for 2 days (less than 30).
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page.
Machine-readable: /api/v1/services/cand_20ac3d7b97f63ee7