api.onesource.io

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

Live, payment required · latest check 2026-10-21 20:06 UTC

As JSON

Returns the deployed bytecode of an Ethereum address via eth_getCode.

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

Placed in Read blockchain data: Node and JSON-RPC access, blocks, transactions, contract reads and explorer data.

GET https://api.onesource.io/api/chain/code/:address$0.003 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 history67 of 67 run

Checks missed46in 30 days

Response, latest65 msto first headers

Schedulehourlyset by usage; rule below

Checked since2026-10-165 days

Freshnessfreshagainst its schedule

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

Response times

Window	Checks	Median	90th	95th	99th	Fastest	Slowest
24 hours	21	83	—	—	—	39	270
7 dayssince 2026-10-17	66	84	211	—	—	24	270
30 dayssince 2026-10-17	66	84	211	—	—	24	270

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 2026-10-21 20:10 UTC. Definitions and method.

Details

Payment terms

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

The registry's own figures, not our measurements.

Access

Our latest check: Asked for payment (x402, MPP)2026-10-21 20:06 UTC
Stated: not stated
Payment model: Per call (asked for payment for our request)
Currency: USD (USDC, in its payment terms)since 2026-10-17 02:05 UTC

"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/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

When	Result	Networks offered	Time to headers
2026-10-21 20:06 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	65 ms
2026-10-21 19:01 UTC cloudflare:MIA	Live, valid payment request HTTP 402	eip155:8453tempo:4217	270 ms
2026-10-21 17:51 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	122 ms
2026-10-21 16:46 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	153 ms
2026-10-21 15:41 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	53 ms
2026-10-21 14:36 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	71 ms
2026-10-21 13:26 UTC cloudflare:MIA	Live, valid payment request HTTP 402	eip155:8453tempo:4217	131 ms
2026-10-21 11:51 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	48 ms
2026-10-21 10:05 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	58 ms
2026-10-21 08:50 UTC cloudflare:MIA	Live, valid payment request HTTP 402	eip155:8453tempo:4217	211 ms
2026-10-21 07:35 UTC cloudflare:MIA	Live, valid payment request HTTP 402	eip155:8453tempo:4217	254 ms
2026-10-21 06:25 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	106 ms
2026-10-21 05:06 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	125 ms
2026-10-21 04:01 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	83 ms
2026-10-21 02:55 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	82 ms
2026-10-21 01:51 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	117 ms
2026-10-21 00:40 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	39 ms
2026-10-20 23:35 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	53 ms
2026-10-20 22:30 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	55 ms
2026-10-20 21:20 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	110 ms
2026-10-20 20:10 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	80 ms
2026-10-20 19:05 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	74 ms
2026-10-20 18:00 UTC cloudflare:MIA	Live, valid payment request HTTP 402	eip155:8453tempo:4217	252 ms
2026-10-20 16:55 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	188 ms
2026-10-20 15:45 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	68 ms
2026-10-20 14:40 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	109 ms
2026-10-20 13:30 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	98 ms
2026-10-20 12:15 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	65 ms
2026-10-20 06:45 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	48 ms
2026-10-19 05:25 UTC cloudflare:EWR	Live, valid payment request HTTP 402	eip155:8453tempo:4217	29 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 5 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_66667c7b912151a1