signals optimal order routing derived
apexrunner.aiMarket dataderived
GET https://apexrunner.ai/signals/optimal-order-routing
passlisted in Coinbase#24 by calls of 44 on this host
0.007 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-07 07:04 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.007 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 2 times across 106 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.
Among the 44 endpoints on apexrunner.ai, signals optimal order routing is tied 24th by calls with 19 others.
The request to signals optimal order routing is the query parameters coin, side and size_usd.
signals optimal order routing returns json; the example shows order_type, recommended_exchange and estimated_total_cost_pct.
The registry's counters give signals optimal order routing 2 calls and 2 unique payers over 30 days, every call from a different payer.
signals optimal order routing was last called 1 day before the snapshot.
Per call, signals optimal order routing declares 0.007 USDC on Base.
TOLL files signals optimal order routing under market data: a GET endpoint on apexrunner.ai, listed in the Coinbase registry.
signals optimal order routing answered the sweep of 2026-10-07 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to signals optimal order routing within market data: payment at www.api-xpay.com and stonk yield invoke at api.solenrich.com.
signals optimal order routing is priced above 31% of comparable listings in market data.
The wallet paid by signals optimal order routing is the payee of 52 endpoints on one host.
In the registry the seller files signals optimal order routing as "execution".
Exactly this price appears on 55 other listings in market data.
the payment options, as of 2026-10-07 23:04 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.007 USDC | exact | 0x8D0663…3E8854 |
the checks, as of 2026-10-07 09:41 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-07 09:41 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 10:27 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 09:21 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 11:38 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 06:15 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 15:27 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:17 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:39 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:53 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 12:41 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 21:23 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 06:56 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 07:08 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 07:31 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 05:33 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 14:00 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 05:25 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 05:25 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 05:42 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:15 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:11 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:27 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:12 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-10-07 07:04 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"coin": "BTC",
"side": "buy",
"size_usd": 1000
}
},
"output": {
"type": "json",
"reason": "string — plain-English explanation of routing decision",
"example": {
"order_type": "limit",
"recommended_exchange": "hyperliquid",
"estimated_total_cost_pct": 0.14
},
"order_type": "string — recommended order type: limit or market",
"venue_ranking": "array — all venues ranked by total cost, each with exchange and total_cost_pct",
"estimated_fee_pct": "float — exchange fee as percentage of order value",
"recommended_exchange": "string — cheapest venue: kraken / coinbase / hyperliquid",
"estimated_total_cost_pct": "float — fee + slippage as percentage of order value"
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-07 23:04 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "signals optimal order routing on apexrunner.ai", snapshot of 2026-10-07 23:04 UTC. https://tollindex.com/e/apexrunner-ai-signals-optimal-order-routing-83ac68/at/2026-10-07T23-04Z. Accessed [access date].
BibTeX
@misc{toll-e-apexrunner-ai-signals-optimal-order-routing-83ac68-2026-10-07T23-04Z,
author = {TOLL},
title = {signals optimal order routing on apexrunner.ai},
howpublished = {\url{https://tollindex.com/e/apexrunner-ai-signals-optimal-order-routing-83ac68/at/2026-10-07T23-04Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-07 23:04 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.