passabsent from every registry#4 by calls of 4 on this host
0.01 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-16 21:17 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / — / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-01 12:09 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
At api.usenami.io, orderbook multi venue execution takes GET requests, is listed in neither registry at the last pull, and falls under compute by TOLL's rules.
orderbook multi venue execution is priced at 0.01 USDC on Base.
Callers of orderbook multi venue execution supply the query parameters ticker and size_usd.
orderbook multi venue execution returns json; the example shows route, ticker, size_usd, naive_note, venues_used, unfilled_usd and 2 others.
orderbook multi venue execution answered the sweep of 2026-09-16 with a valid 402, as at every sweep since 2026-09-11.
orderbook multi venue execution is one of 4 listed endpoints on api.usenami.io, tied 4th by calls with 1 other among them.
orderbook multi venue execution takes 5% of the calls counted across api.usenami.io.
In the trailing 30 days: one call, one payer.
orderbook multi venue execution was last called 62 days before the snapshot.
Closest in price to orderbook multi venue execution within compute: starcloud orbital compute test mid at smx.space and route execute at agent402.tools.
orderbook multi venue execution is priced above 42% of comparable listings in compute.
Its payee wallet receives for 29 listed endpoints on one host.
The seller's tags on orderbook multi venue execution are funding, perpetual, trading and multi-venue.
orderbook multi venue execution was missing from the Coinbase registry at the pull of 2026-09-17, confirmed at the pull of 2026-09-17; that is registry presence, not liveness.
The price of orderbook multi venue execution is declared by 230 other listings in compute too.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-09-16 21:17 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x153872…10475c |
the checks, as of 2026-09-16 06:11 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-16 06:11 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:28 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:57 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:50 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:07 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 12:05 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-01 12:09 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"ticker": {
"type": "string",
"required": true,
"description": "Base ticker. Required."
},
"size_usd": {
"enum": [
1000,
5000,
10000
],
"type": "integer",
"required": false,
"description": "Notional size. Default 10000."
}
}
},
"output": {
"type": "json",
"example": {
"route": [
{
"venue": "binance",
"best_ask": 104251,
"best_bid": 104250.5,
"slippage_bps": 1.2,
"allocated_usd": 10000,
"max_fillable_usd": 220000
}
],
"ticker": "BTC",
"size_usd": 10000,
"naive_note": "Excludes fees/funding/latency — baseline only.",
"venues_used": 1,
"unfilled_usd": 0,
"total_filled_usd": 10000,
"blended_slippage_bps": 1.2
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "orderbook multi venue execution on api.usenami.io". https://tollindex.com/e/api-usenami-io-v1-orderbook-multi-venue-execution-c457f0. Accessed [access date].
BibTeX
@misc{toll-e-api-usenami-io-v1-orderbook-multi-venue-execution-c457f0-2026-11-02,
author = {TOLL},
title = {orderbook multi venue execution on api.usenami.io},
howpublished = {\url{https://tollindex.com/e/api-usenami-io-v1-orderbook-multi-venue-execution-c457f0}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-02 05:58 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.