Web read x402 REST usage
Read a web page and extract content as markdown with screenshot
0.002 USDC per call
per call
← All services
Daily transfers, volume and coverage →
Apify Actor Preflight
x402 resource x402 RESTaudit-tools.ai · audit-tools.ai · Web & Scraping
Vet an Apify actor before you spend on it. Send one actor ID (e.g. apify/instagram-scraper) and get scored JSON in seconds, with evidence and a verdict, from public metadata: pricing, output schema, maintenance, reliability, docs. Unlimited criteria: our pre-built set or your own rubric in plain Eng
Price per call
0.02 USDC per call
published unit: per call
Calls · 30d
3
counted by the source, no daily split
Payers · 30d
3
distinct paying addresses seen by the source
Observed inflows · 30d
$0.06
3 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.02USD observed / day
2026-10-01grey = not scanned · UTC days2026-10-30
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-30) | $0.00 | 0 |
| Last 7 days | $0.02 | 1 |
| Last 30 days | $0.06 | 3 |
| 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 | 0x95de884e9eb3f90e496200693d94a636942a130d | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
Sending wallets · observed counterparties
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
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
Web & Scraping
- Web read 6,609 calls · 0.002 USDC per call —
- Domain WHOIS & DNS Lookup 449 calls · 0.02 USDC per call —
- Base64 encode url 448 calls · 0.0216 USDC per call —
- Agent Web-Access 378 calls · 0.001 USDC per call —
- Random Fact 312 calls · 0.01 USDC per call $4.15
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,065 services in this category
| With a measured call count | 1,688 (27.8 %) |
|---|---|
| With a published price | 2,200 (36.3 %) |
| With attributable inflows | 60 (1.0 %) |
| Observed inflows · 30d | $277.00 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Similar services
All of Web & Scraping →Domain WHOIS & DNS Lookup x402 REST usage
Domain WHOIS and DNS lookup. Registrar, creation and expiry dates, nameservers, and full DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain.
0.02 USDC per call
per call
Base64 encode url x402 REST usage
URL to Base64: Fetch a file from a URL and return it as base64 with its content type and a data URI, ready to embed.
0.0216 USDC per call
per call
Agent Web-Access x402 REST usage
Web scraping API for AI agents: read any live web page as clean markdown, text or HTML. Renders JavaScript in our own headless browser, then strips navigation, ads and boilerplate. Use it when a plain HTTP GET returns em...
0.001 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.02 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 20000 = 0.02 USDC per call on Base.
What you can call
access: payment per call (x402)endpoint
https://audit-tools.ai/api/preflight
Request
{
"body": {
"targets": [
"apify/instagram-scraper"
]
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
Examples are the provider's own, not a call we made.
Opportunity insights
2 findings from measured data-
Two independent sources agree
The observed inflow implies about 3 calls at list price; the source counted 3 (factor 1). A transfer is still not a purchase, but the order of magnitude holds — this is the strongest monetisation signal in the catalogue short of a receipt feed.
Peers with attributed inflows → -
Category benchmark
60 of 6,065 services (1.0%) in Web & Scraping have attributable inflows; 1,688 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →
What the provider says
Vet an Apify actor before you spend on it. Send one actor ID (e.g. apify/instagram-scraper) and get scored JSON in seconds, with evidence and a verdict, from public metadata: pricing, output schema, maintenance, reliability, docs. Unlimited criteria: our pre-built set or your own rubric in plain English. Metadata grades what a vendor claims. The $1 full audit runs the actor and measures what it delivers: real cost per usable item, whether advertised fields arrive, speed and consistency.
Quoted from x402 Bazaar · source record · read 2026-10-31
Facts and where they come from
- Price
-
0.02 USDC per call
Provider claim
Recorded value: 0.02 USDC per call.
- Unit
- per call
- Protocol
- x402, REST · transport: HTTP Provider claim
- Auth
- x402
- Endpoint
- https://audit-tools.ai/api/preflight
- 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
- 3 calls · 3 unique payers in the 30 days before 2026-10-27. 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.06
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.06 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 3 calls; the source counted 3. 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
0x95de884E9eb3F90E496200693d94a636942a130D
0.02 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://audit-tools.ai/api/preflight
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 0x95de884E9eb3F90E496200693d94a636942a130D
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.02 USDC per call
EvidenceAtomic amount 20000 = 0.02 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 |
audit-tools.ai
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 |
3 calls / 3 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-26T18:52:01.932Z. 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.