passlisted in Coinbase#9 by calls of 14 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-08 06:11 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 4
How has the volume on this endpoint moved?
Among the 14 endpoints on api.munition.io, exa answer is tied 9th by calls with 3 others.
Requests carry a json body with the fields text and query.
exa answer returns json; the example shows meta, query, answer and citations.
The registry's counters give exa answer 2 calls and 2 unique payers over 30 days, every call from a different payer.
exa answer was last called 5 days before the snapshot.
Per call, exa answer declares 0.01 USDC on Base.
It accounts for 3% of the calls counted across the host.
For exa answer the listing declares 4 accepts on Base, Polygon, Arbitrum and Solana, to 2 different wallets.
TOLL files exa answer under inference: a POST endpoint on api.munition.io, listed in the Coinbase registry.
exa answer answered the sweep of 2026-10-19 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to exa answer within inference: ai news at api.losbeto.xyz and agent analyse at api.zendiq.ai.
Among comparable prices in inference, exa answer sits above 14% of them.
The wallet paid by exa answer is the payee of 14 endpoints on one host.
It disappeared from the registry on 2026-10-04 and returned on 2026-10-04.
The price of exa answer is declared by 6,800 other listings in inference too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x54d6C2…1A4aFa |
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x54d6C2…1A4aFa |
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x54d6C2…1A4aFa |
| Coinbase | solana: | USDC | 0.01 USDC | exact | CawPXxAT…kbDyDo |
the checks, as of 2026-10-19 07:25 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-19 07:25 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 09:32 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 19:38 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 05:44 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 07:24 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 05:36 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 10:13 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 07:35 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 06:09 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 14:17 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 06:40 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 08:08 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 07:24 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 08:12 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 07:33 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 10:10 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 05:07 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 14:25 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 07:23 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 06:41 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:00 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 05:48 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 20:32 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 06:10 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 06:21 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 06:43 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-20 19:22 UTC | pass | 0 | daily-2026-09-20 |
| 2026-09-19 04:45 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 10:39 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 04:41 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 04:41 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 04:39 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:34 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:33 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:49 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:22 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 06:11 UTC · method · live
The input and output block
{
"input": {
"body": {
"text": false,
"query": "Who maintains the x402 protocol?"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"meta": {
"answeredAt": "2026-09-09T00:00:00.000Z",
"citationCount": 1
},
"query": "Who maintains the x402 protocol?",
"answer": "x402 was created by Coinbase and is developed as an open standard.",
"citations": [
{
"url": "https://www.x402.org/",
"title": "x402"
}
]
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "exa answer on api.munition.io", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-munition-io-v1-exa-answer-49897a/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-munition-io-v1-exa-answer-49897a-2026-10-13T14-08Z,
author = {TOLL},
title = {exa answer on api.munition.io},
howpublished = {\url{https://tollindex.com/e/api-munition-io-v1-exa-answer-49897a/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.