Exa x402 REST usage
Exa /search endpoint
Daily transfers, volume and coverage →
x402.agentindex.world · x402.agentindex.world · Search & Research
Jev-powered research: routed search, cited answer, claims verified against sources. Ask a question, get a 5-8 sentence answer, each claim tagged to a numbered source, built from real page content - no invented facts. A fast paid LLM writes it, under 4.5s guaranteed; on a rare miss, a no-LLM extracti
The payout address is also published by 116 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-31) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0xb3f32bdfe8d07825bc0d7387295ab1d7559ba69d | Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar |
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 10,602 (61.2 %) |
|---|---|
| With a published price | 11,106 (64.1 %) |
| With attributable inflows | 113 (0.7 %) |
| Observed inflows · 30d | $3,443.91 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Exa /search endpoint
Web search built for agents, served over Pocket Network: POST /v1/search with a query and an optional max_results, and get the results back as one JSON object. Results vary run to run, as web search does. GET /v1/version...
Search cached Seats.aero award availability by origin, destination, dates, cabin, carriers, and pagination.
Search Twitter/X tweets with advanced filters. Returns up to 20 tweets per page, most recent first, with pagination. At least one filter required. Params: words, phrase, anyWords, noneWords, hashtags, from, to, mentionin...
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.005 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 5000 = 0.005 USDC per call on Base.
endpoint
https://x402.agentindex.world/research
{
"body": {
"query": "What are the main features of the Rust programming language?"
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"answer": "The main features of the Rust programming language include an emphasis on performance, type safety, concurrency, and memory safety [1]. Rust supports multiple programming paradigms [1]. The language's syntax is heavily influenced by C++ and functional programming languages such as OCaml [2]. Rust has a focus on static typing and a borrow system, similar to other systems programming languages [5]. However, sources [3] and [4] do not provide information about Rust, instead discussing other programming languages, Zig and V, respectively. Overall, the sources suggest that Rust is a systems programming language with a strong focus on safety and performance [1][2][5].",
"claims_verified": true,
"claims_verified_reason": null,
"query": "What are the main features of the Rust programming language?",
"sources": [
{
"published_at": null,
"source": "wikipedia",
"title": "Rust (programming language)",
"url": "https://en.wikipedia.org/wiki/Rust_(programming_language)"
},
{
"published_at": null,
"source": "wikipedia",
"title": "Rust syntax",
"url": "https://en.wikipedia.org/wiki/Rust_syntax"
},
{
"published_at": null,
"source": "wikipedia",
"title": "Zig (programming language)",
"url": "https://en.wikipedia.org/wiki/Zig_(programming_language)"
},
{
"published_at": null,
"source": "wikipedia",
"title": "V (programming language)",
"url": "https://en.wikipedia.org/wiki/V_(programming_language)"
},
{
"published_at": null,
"source": "wikipedia",
"title": "Mojo (programming language)",
"url": "https://en.wikipedia.org/wiki/Mojo_(programming_language)"
}
],
"synthesis": "llm",
"timing_ms": {
"search": 1230,
"synthesis": 644,
"total": 2160,
"verify": 287
}
},
"type": "json"
}
Examples are the provider's own, not a call we made.
The payout address is shared with 116 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.
How attribution works →113 of 17,332 services (0.7%) in Search & Research have attributable inflows; 10,602 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Jev-powered research: routed search, cited answer, claims verified against sources. Ask a question, get a 5-8 sentence answer, each claim tagged to a numbered source, built from real page content - no invented facts. A fast paid LLM writes it, under 4.5s guaranteed; on a rare miss, a no-LLM extractive fallback (top sentences from the sources, picked by Jev) takes over instead, marked "synthesis":"extractive". Try GET /research/sample.
Quoted from x402 Bazaar · source record · read 2026-10-31
Attribution blocked
· confidence low
The payout address is also published by 116 other service(s); the volume cannot be attributed to one of them.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is an activity value of $0.02 — the source's call count multiplied by the published price. That is what the list price implies, not what anyone paid. The payout address is also published by 116 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://x402.agentindex.world/research
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-31 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-31 |
| Payment | Provider claim |
1 rail: Base · payee 0xb3F32bdfe8D07825BC0D7387295aB1D7559BA69d
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-31 |
| Pricing | Provider claim |
0.005 USDC per call
EvidenceAtomic amount 5000 = 0.005 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-31 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-31 |
| Provider | Provider claim |
x402.agentindex.world
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-31 |
| Usage | Verified |
3 calls / 3 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-31. Letzter Aufruf laut Quelle: 2026-10-20T07:40:10.359Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-31 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.