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
Menu

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

GET https://api.onesource.io/api/chain/network-info$0.001 per call · from the registry's payment terms

The name is the registry's label, not ours. Not reviewed by a person. See 80 endpoints from onesource.io.

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 history35 of 35 run
Checks missed11in 30 days
Response, latest70 msto first headers
Schedulehourlyset by usage; rule below
Checked since2026-10-162 days
Freshnessfreshagainst its schedule

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

Details

Payment terms

Price per call
$0.001
Protocols
x402, mpp
Networks
eip155:8453tempo:4217
Terms changes, 90 days
0 in 2 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
218
Paid calls, 30 days
233

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)

"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 / Crypto and on-chain data / Read blockchain data (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/3): ✓ 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 70 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 200 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 113 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 38 ms

cloudflare:EWR		 Live, valid payment request HTTP 402 eip155:8453tempo:4217 110 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 243 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 96 ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

cloudflare:EWR		 Live, valid payment request HTTP 402 eip155:8453 80 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 2 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_cb63fae8b6d8c702