api.onesource.io
Paid API · api.onesource.io · found in a public registry · checked since 2026-10-16
Live, payment required · latest check
GET https://api.onesource.io/api/chain/chain-id$0.001 per call · from the registry's payment termsThe 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 AmericaLast 30 checks, oldest to newest
30 passed, 0 failed, 0 not run.
Checked hourly. Hourly: 100 or more distinct payers in the last 30 days, as reported by the registry.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 20 | 0 | 86 | — | — | — | 33 | 212 |
| 7 dayssince 2026-10-17 | 36 | 0 | 86 | — | — | — | 29 | 214 |
| 30 dayssince 2026-10-17 | 36 | 0 | 86 | — | — | — | 29 | 214 |
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.001
- Protocols
- x402, mpp
- Networks
- eip155:8453tempo:4217
- Terms changes, 90 days
- 0 in 3 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
- 163
- 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)
"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/4): ✓ 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
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 57 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 102 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 89 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 90 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 71 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 76 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 143 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 119 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 46 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 212 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 86 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 195 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 123 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 33 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 52 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453tempo:4217 | 131 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 84 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 51 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 48 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 119 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 33 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 48 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 74 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 183 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 30 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 69 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 45 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 43 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 29 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 114 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_f0045408c4d9d302