Events x402 REST usage
Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range
0.005 USDC per call
per call
← All services
Daily transfers, volume and coverage →
Agent Web Tools
x402 resource x402 RESTagent-web-tools.agent-web-tools.workers.dev · agent-web-tools.agent-web-tools.workers.dev · Infrastructure
not indexed
Provider site ↗
Check if a URL is up: status, latency, redirects, title.
Price per call
0.001 USDC per call
published unit: per call
Calls · 30d
71
counted by the source, no daily split
Payers · 30d
12
distinct paying addresses seen by the source
Observed inflows · 30d
$0.234
105 transfers to the payout address
Inflow growth · 7d
—
not comparable (baseline under $1 or window incomplete)
Payment evidence
Observed transfers
confidence: medium
· read 2026-10-31
Observed inflows · last 30 days
$0.19USD observed / day
2026-10-01grey = not scanned · UTC days2026-10-30
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-30) | $0.005 | 5 |
| Last 7 days | $0.206 | 100 |
| Last 30 days | $0.234 | 105 |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Blockchain wallets
Full addresses · public payment evidenceReceiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
Receiving wallets · provider payment addresses
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0xf22b154e0858c97c42cc4a1151e26ea1797fa6c3 | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
Sending wallets · observed counterparties
All 6 retained sending addresses are listed below. Source: on-chain transfer scans. Dates are UTC days.
| Network | Full wallet address | Transfers | First / last observed | Last scanned (UTC) |
|---|---|---|---|---|
| Base | 0x35fe83e85f949b7235595a76782296c6c9c3c030 | 1 | 2026-10-30 / 2026-10-30 | 2026-10-31 11:38:13 |
| Base | 0x73cc9400bd9f086d7427d3421d79195a68bb1ea4 | 1 | 2026-10-31 / 2026-10-31 | 2026-10-31 11:42:40 |
| Base | 0x8ec901f7e2710163387d70950f680f1ea2269d15 | 2 | 2026-10-30 / 2026-10-31 | 2026-10-31 11:42:40 |
| Base | 0xa1d1c0cf717402ff3651aa4873ccf96410b01978 | 1 | 2026-10-30 / 2026-10-30 | 2026-10-31 11:38:13 |
| Base | 0xaa34bd941511cc82a19878e2efbe0bd7077e1db3 | 3 | 2026-10-29 / 2026-10-30 | 2026-10-31 11:38:13 |
| Base | 0xf1f15ab1b66377d6d60b8938a737122551be57f9 | 1 | 2026-10-29 / 2026-10-29 | 2026-10-30 23:38:16 |
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Competitors & category benchmark
Rank the whole category →
Closest competitors
Infrastructure
- Events 228 calls · 0.005 USDC per call —
- Pulse 62 calls · 0.003 USDC per call —
- StableStudio 59 calls · 0.01 USDC per call —
- neo timestamp 57 calls · 0.01 USDC per call —
- Reserved 38 calls · 0.01 USDC per call —
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
Category benchmark
6,045 services in this category
| With a measured call count | 961 (15.9 %) |
|---|---|
| With a published price | 1,104 (18.3 %) |
| With attributable inflows | 20 (0.3 %) |
| Observed inflows · 30d | $70.01 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Similar services
All of Infrastructure →Pulse x402 REST usage
China pulse, cheap enough to POLL: what China is talking about RIGHT NOW and what is NEW since your last call - built for agents that monitor continuously. Returns `consensus` (phrases trending on 2+ of Weibo/Baidu/Douyi...
0.003 USDC per call
per call
StableStudio x402 REST usage
Get a client token for direct upload to Vercel Blob
0.01 USDC per call
per call
neo timestamp x402 REST usage
Prove you had this sha256 at this time: signed receipt with its position in neo's public log, anchored daily on Bitcoin (OpenTimestamps) and Software Heritage.
0.01 USDC per call
per call
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
Service details, payment routes and source evidence
Where you can pay
1 route from the provider's payment requirements| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.001 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 1000 = 0.001 USDC per call on Base.
What you can call
access: payment per call (x402)endpoint
https://agent-web-tools.agent-web-tools.workers.dev/v1/check
Request
{
"method": "GET",
"queryParams": {
"url": "https://example.com"
},
"type": "http"
}
Response
{
"example": {
"checkedAt": "2026-10-14T00:00:00.000Z",
"contentType": "text/html",
"finalUrl": "https://example.com/",
"https": true,
"latencyMs": 120,
"redirects": [],
"server": "cloudflare",
"status": 200,
"title": "Example Domain",
"up": true,
"url": "https://example.com"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
Opportunity insights
2 findings from measured data-
Call count and inflow disagree
The observed inflow implies about 234 calls at list price; the source counted 71 (factor 3). Either the effective price differs from the list price, or part of the volume belongs to other payers on the same address. Do not read the inflow as this service's revenue.
Peers with attributed inflows → -
Category benchmark
20 of 6,045 services (0.3%) in Infrastructure have attributable inflows; 961 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →
What the provider says
Check if a URL is up: status, latency, redirects, title.
Quoted from x402 Bazaar · source record · read 2026-10-31
Facts and where they come from
- Price
-
0.001 USDC per call
Provider claim
Recorded value: 0.001 USDC per call.
- Unit
- per call
- Protocol
- x402, REST · transport: HTTP Provider claim
- Auth
- x402
- Source
- x402 Bazaar (Coinbase CDP) · Public discovery API (provider-published records)
- Last checked
- Not checked by us yet — the data is as the source published it
- First seen
- 2026-10-24
- Usage
- 71 calls · 12 unique payers in the 30 days before 2026-10-31. Measured by the x402 Bazaar, not by us and not by the provider.
Money, and what it actually proves
Verified revenue · 30d
Unknown
Observed inflows · 30d
$0.234
Attribution
Exclusive
Receipt ledger
Not connected
Observed transfers
· confidence medium
Token transfers reached this service's own payout address. A transfer is not a purchase, and shared, refunded or unrelated transfers cannot be excluded.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is $0.234 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.
Cross-check. At the published price the observed inflow would cover about 234 calls; the source counted 71. Two independent measurements of the same question — they never match exactly, because the effective price differs per call size and the address can also receive unrelated transfers.
Daily market statistics — the ledger view, day by day
No daily history has been archived for this service yet. Open the full daily history →
Payment rails
Base
· exact · USDC
0xF22b154E0858c97c42CC4a1151e26Ea1797fa6C3
0.001 USDC
From source record
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
Provenance
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://agent-web-tools.agent-web-tools.workers.dev/v1/check
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-31 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-31 |
| Payment | Provider claim |
1 rail: Base · payee 0xF22b154E0858c97c42CC4a1151e26Ea1797fa6C3
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-31 |
| Pricing | Provider claim |
0.001 USDC per call
EvidenceAtomic amount 1000 = 0.001 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-31 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-31 |
| Provider | Provider claim |
agent-web-tools.agent-web-tools.workers.dev
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-31 |
| Usage | Verified |
71 calls / 12 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-31. Letzter Aufruf laut Quelle: 2026-10-31T00:41:03.373Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-31 |
Endpoint checks
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.