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.
View daily earnings, market cap, volume and coverage →
win.oneshotagent.com · win.oneshotagent.com · Web & Scraping
| Day · UTC | Earned | Gross volume | Refunds | Observed transfers | Market cap | Revenue coverage |
|---|---|---|---|---|---|---|
| 2026-10-25 | — | — | — | — | — | none |
| 2026-10-24 | — | — | — | — | — | none |
| 2026-10-23 | — | — | — | — | — | none |
| 2026-10-22 | — | — | — | — | — | none |
| 2026-10-21 | — | — | — | — | — | none |
| 2026-10-20 | — | — | — | — | — | none |
| 2026-10-19 | — | — | — | — | — | none |
View daily history → · UTC days; today's figures are partial.
Read a web page and extract content as markdown with screenshot
Quoted from x402 Bazaar · source record · read 2026-10-25
No settled payment on record. Earnings for this service are unknown — not zero. The source counts 9,788 calls in 30 days, which at the published price is roughly $19.58 of activity. Activity is not revenue; no charge has been reconciled for it.
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.
{
"body": {
"url": "https://example.com"
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"markdown": "# Example Domain",
"metadata": {
"description": "",
"statusCode": 200,
"title": "Example Domain"
},
"receipt_id": "uuid",
"request_id": "uuid",
"screenshot_url": "https://...",
"status": "completed",
"tool": "web_read",
"truncated": false,
"url": "https://example.com"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
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://win.oneshotagent.com/v1/tools/web-read
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-25 |
| 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-25 |
| Payment | Provider claim |
1 rail: Base · payee 0x9fb365E4E9385E2a39FeBAd70368267e6f571d9A
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-25 |
| Pricing | Provider claim |
0.002 USDC per call
EvidenceAtomic amount 2000 = 0.002 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-25 |
| 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-25 |
| Provider | Provider claim |
win.oneshotagent.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-25 |
| Usage | Verified |
9,788 calls / 22 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-25. Letzter Aufruf laut Quelle: 2026-10-25T10:32:05.907Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-25 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.
Domain WHOIS and DNS lookup. Registrar, creation and expiry dates, nameservers, and full DNS records (A, AAAA, MX, NS, TXT, CNAME) for a domain.
Read any live web page as clean, LLM-ready text. Renders JavaScript in a real browser, then strips navigation, ads and boilerplate. Use it when a plain HTTP GET returns empty or garbled HTML: single-page apps, dynamic fe...
Returns a single random fact as JSON in exchange for a micropayment.
Extract named fields from unstructured text into strict JSON. Use when an agent must turn an email, filing, invoice, or description into {field: value} records up to 4,000 characters.
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.