Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

api.onesource.io

Paid API · api.onesource.io · found in a public registry · checked since 2026-10-16

Live, payment required · latest check

As JSON

Returns the newest trades for a Deepstate market, newest first.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means

Placed in Decentralised finance: Decentralised finance protocols, liquidity and trading data.

GET https://api.onesource.io/deepstate/v1/trades/:book$0.005 per call · from the registry's payment terms

The name is the registry's label, not ours. Not reviewed by a person. See 81 endpoints from onesource.io. The URL contains placeholders (such as :address) that callers fill in.

Our checks

An unpaid request hourly, from eastern North America

Last 30 checks, oldest to newest

30 passed, 0 failed, 0 not run.

Passed, 30 daysshort history42 of 42 run
Checks missed41in 30 days
Response, latest111 msto first headers
Schedulehourlyset by usage; rule below
Checked since2026-10-164 days
Freshnessfreshagainst its schedule

Checked hourly. Hourly: 100 or more distinct payers in the last 30 days, as reported by the registry.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hours30——————
7 dayssince 2026-10-1741089———23289
30 dayssince 2026-10-1741089———23289

Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Payment terms

Price per call
$0.005
Protocols
x402, mpp
Networks
eip155:8453tempo:4217
Terms changes, 90 days
0 in 4 days tracked

Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-17; 0 receiving-address changes. Definitions

Reported by the registry

Payers, 30 days
179
Paid calls, 30 days
179

The registry's own figures, not our measurements.

Access

Our latest check
Asked for payment (x402, MPP)
Stated
not stated
Payment model
Per call (asked for payment for our request)
Currency
USD (USDC, in its payment terms)since

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Listing

In the capability tree: Financial and economic data / Decentralised finance (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-19. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed; ✓ at least 5 payers in 30 days (registry figure).

Purpose tags: none in the registry

Recent probes

WhenResultNetworks offeredTime to headers

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 111 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 31 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 95 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 50 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 117 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 118 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 113 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 101 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 127 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 67 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 129 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 49 ms

cloudflare:MIA
Live, valid payment request HTTP 402 eip155:8453tempo:4217 289 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 36 ms

cloudflare:MIA
Live, valid payment request HTTP 402 eip155:8453tempo:4217 235 ms

cloudflare:MIA
Live, valid payment request HTTP 402 eip155:8453tempo:4217 91 ms

cloudflare:MIA
Live, valid payment request HTTP 402 eip155:8453tempo:4217 242 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 45 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 26 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 51 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453tempo:4217 45 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 77 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 134 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 23 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 113 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 69 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 77 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 56 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 60 ms

cloudflare:EWR
Live, valid payment request HTTP 402 eip155:8453 53 ms

What these figures do not show

  • A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). It does not show that a paid call succeeds or returns useful results.
  • Payer and call counts are the registry's own figures, not our measurements.
  • The registry's description is not republished.
  • Limited evidence: monitored for 4 days (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_d54b9263e1d3e843