TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-29 · finished 2026-10-29 12:42 UTC
Listed
32,435

signals slippage forecast derived

apexrunner.aiMarket dataderived

GET https://apexrunner.ai/signals/slippage-forecast

passlisted in Coinbase#22 by calls of 44 on this host

0.007 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-29 06:27 UTC · method · pinnable · sweep daily-2026-10-29
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-29 06:27 UTC · method · pinnable · 6 of 6 in 7d, 29 of 29 in 30d, 45 of 45 in 90d
Calls, trailing 30 days
2
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
2
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-08 06:26 UTC
as of 2026-10-13 14:08 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.007 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

122 observations, 4 of them a change

How has the volume on this endpoint moved?

123210 Sep11 Sep12 Sep13 Sep14 Sep15 Sep16 Sep17 Sep18 Sep19 Sep20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep26 Sep27 Sep28 Sep29 Sep30 Sep1 Oct2 Oct3 Oct4 Oct5 Oct6 Oct7 Oct8 Oct9 Oct10 Oct11 Oct12 Oct13 Oct
Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot.

In words

Among the 44 endpoints on apexrunner.ai, signals slippage forecast is tied 22nd by calls with 16 others.

Requests carry the query parameters coin, side and size_usd.

signals slippage forecast returns json; the example shows order_size_usd, recommendation, liquidity_condition and expected_slippage_pct.

The registry's counters give signals slippage forecast 2 calls and 2 unique payers over 30 days, every call from a different payer.

signals slippage forecast was last called 5 days before the snapshot.

Per call, signals slippage forecast declares 0.007 USDC on Base.

TOLL files signals slippage forecast under market data: a GET endpoint on apexrunner.ai, listed in the Coinbase registry.

signals slippage forecast answered the sweep of 2026-10-29 with a valid 402, as at every sweep since 2026-09-11.

Closest in price to signals slippage forecast within market data: wallet pnl at scry.solanahub.de and chain tx at api.onesource.io.

signals slippage forecast is priced above 37% of comparable listings in market data.

The wallet paid by signals slippage forecast is the payee of 52 endpoints on one host.

In the registry the seller files signals slippage forecast as "execution".

Exactly this price appears on 57 other listings in market data.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.007 USDCexact0x8D0663…3E8854

Preflight checks at the last sweep

the checks, as of 2026-10-29 06:27 UTC · method · pinnableendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-29 06:27 UTCpass0daily-2026-10-29
2026-10-28 06:49 UTCpass0daily-2026-10-28
2026-10-27 06:42 UTCpass0daily-2026-10-27
2026-10-26 12:03 UTCpass0daily-2026-10-26
2026-10-24 21:24 UTCpass0daily-2026-10-24
2026-10-23 06:37 UTCpass0daily-2026-10-23
2026-10-22 04:51 UTCpass0daily-2026-10-22
2026-10-21 08:35 UTCpass0daily-2026-10-21
2026-10-20 08:45 UTCpass0daily-2026-10-20
2026-10-19 06:20 UTCpass0daily-2026-10-19
2026-10-18 08:32 UTCpass0daily-2026-10-18
2026-10-17 18:33 UTCpass0daily-2026-10-17
2026-10-16 04:46 UTCpass0daily-2026-10-16
2026-10-15 06:21 UTCpass0daily-2026-10-15
2026-10-14 04:43 UTCpass0daily-2026-10-14
2026-10-13 09:11 UTCpass0daily-2026-10-13
2026-10-12 06:35 UTCpass0daily-2026-10-12
2026-10-11 04:58 UTCpass0daily-2026-10-11
2026-10-10 13:08 UTCpass0daily-2026-10-10
2026-10-09 05:08 UTCpass0daily-2026-10-09
2026-10-08 06:46 UTCpass0daily-2026-10-08
2026-10-07 05:55 UTCpass0daily-2026-10-07
2026-10-06 06:50 UTCpass0daily-2026-10-06
2026-10-05 06:29 UTCpass0daily-2026-10-05
2026-10-04 09:16 UTCpass0daily-2026-10-04
2026-10-03 04:27 UTCpass0daily-2026-10-03
2026-10-02 13:38 UTCpass0daily-2026-10-02
2026-10-01 06:49 UTCpass0daily-2026-10-01
2026-09-30 06:06 UTCpass0daily-2026-09-30
2026-09-29 18:27 UTCpass0daily-2026-09-29
2026-09-28 04:18 UTCpass0daily-2026-09-28
2026-09-25 20:01 UTCpass0daily-2026-09-25
2026-09-23 05:42 UTCpass0daily-2026-09-23
2026-09-22 05:52 UTCpass0daily-2026-09-22
2026-09-21 06:15 UTCpass0daily-2026-09-21
2026-09-20 18:54 UTCpass0daily-2026-09-20
2026-09-19 04:16 UTCpass0daily-2026-09-19
2026-09-18 10:01 UTCpass0daily-2026-09-18
2026-09-17 04:14 UTCpass0daily-2026-09-17
2026-09-16 04:15 UTCpass0daily-2026-09-16
2026-09-15 04:13 UTCpass0daily-2026-09-15
2026-09-14 04:11 UTCpass0daily-2026-09-14
2026-09-13 04:10 UTCpass0daily-2026-09-13
2026-09-12 06:26 UTCpass0daily-2026-09-12
2026-09-11 09:54 UTCpass0daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-08 06:26 UTC · method · live

The input and output block
{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "coin": "BTC",
      "side": "buy",
      "size_usd": 1000
    }
  },
  "output": {
    "type": "json",
    "example": {
      "order_size_usd": 10000,
      "recommendation": "split_order",
      "liquidity_condition": "MODERATE",
      "expected_slippage_pct": 0.12
    },
    "order_size_usd": "float — order size used for slippage estimate in USD",
    "recommendation": "string — execute_now, split_order, or wait_for_liquidity",
    "slippage_cost_usd": "float — predicted slippage cost in USD",
    "liquidity_condition": "string — DEEP / MODERATE / THIN based on current order book depth",
    "expected_slippage_pct": "float — predicted slippage as percentage of order value"
  }
}
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, "signals slippage forecast on apexrunner.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/apexrunner-ai-signals-slippage-forecast-252f9e/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-apexrunner-ai-signals-slippage-forecast-252f9e-2026-10-13T14-08Z,
  author = {TOLL},
  title = {signals slippage forecast on apexrunner.ai},
  howpublished = {\url{https://tollindex.com/e/apexrunner-ai-signals-slippage-forecast-252f9e/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].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about signals slippage forecast, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 252f9e2b84913670d7eb08fb118356f8741891bf122cb869026c574f6d397063 from wallet 0x8D0663BBb967ebF1c047405A888DDf865f3E8854

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.