Services / API · Registry
api.onesource.io
GET https://api.onesource.io/api/chain/nonce/:address
Listed in a public agent registry. The name is the registry's label, not ours. Not reviewed by a person. See all 80 endpoints from onesource.io. The URL contains placeholders (such as :address) that callers fill in.
Checked hourly. Hourly: 100 or more distinct payers in the last 30 days, as reported by the registry.
In the capability tree: Financial and economic data / Crypto and on-chain 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).
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 246 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 180 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 108 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 91 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 80 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 153 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 30 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 59 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 97 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 87 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 32 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 88 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 47 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 68 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 161 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 188 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 89 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 67 ms |
cloudflare:ATL |
Live, valid payment request HTTP 402 | eip155:8453 | 68 ms |
cloudflare:ATL |
Live, valid payment request HTTP 402 | eip155:8453 | 118 ms |
cloudflare:ATL |
Live, valid payment request HTTP 402 | eip155:8453 | 38 ms |
cloudflare:SCL |
Live, valid payment request HTTP 402 | eip155:8453 | 153 ms |
What this evidence does 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 1 day (less than 30).
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page.
Machine-readable: /api/v1/services/cand_9533e687640bd2cd