passlisted in Coinbase#2 by calls of 3 on this host
0.02 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
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-31 08:30 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.02 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 28 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
TOLL files resolving under market data: a GET endpoint on api.orcatrace.dev, listed in the Coinbase registry.
A call to resolving costs 0.02 USDC on Base, as declared.
resolving takes the query parameters withinHours, includeNoise and minLiquidity.
A response from resolving, as declared, includes data, count, filters and success.
The daily sweep got a valid payment challenge from resolving on 2026-09-15, as at every sweep since 2026-09-11.
resolving is one of 3 listed endpoints on api.orcatrace.dev, tied 2nd by calls with 1 other among them.
resolving takes 1% of the calls counted across api.orcatrace.dev.
In the trailing 30 days: one call, one payer.
resolving was last called 15 days before the snapshot.
Closest in price to resolving within market data: activities smarttraders smartmoney at x402.sniperx.fun and liquidations btc at kronossignals.com.
resolving is priced above 64% of comparable listings in market data.
The wallet paid by resolving is the payee of 9 endpoints across 5 hosts.
Exactly this price appears on 469 other listings in market data.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.02 USDC | exact | 0xf444ab…9514a0 |
the checks, as of 2026-09-15 06:52 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-09-15 06:52 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:19 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:10 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:27 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:36 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-31 08:30 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"withinHours": 24,
"includeNoise": "example",
"minLiquidity": 5000
}
},
"output": {
"type": "json",
"example": {
"data": [
{
"yesMid": 0.83,
"question": "Will X happen by June 14?",
"convergence": "contested",
"eventEndDate": "2026-06-14T00:00:00Z",
"liquidityUsd": 41000,
"hoursRemaining": 22.5
}
],
"count": 1,
"filters": {
"withinHours": 24,
"includeNoise": false,
"minLiquidity": 5000
},
"success": true
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "resolving on api.orcatrace.dev", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-orcatrace-dev-v1-resolving-e76b1b/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-api-orcatrace-dev-v1-resolving-e76b1b-2026-09-15T16-57Z,
author = {TOLL},
title = {resolving on api.orcatrace.dev},
howpublished = {\url{https://tollindex.com/e/api-orcatrace-dev-v1-resolving-e76b1b/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.