api.oassis.dev
No description published for this endpoint.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"notes": [
"Charged up front, one scrape per url. A url that fails outright and a url served from the cache are refunded together when the job ends, as a single movement in your account.",
"A refund is a credit to an API-key account. A wallet payment is settled on-chain and cannot be reversed from here, so paying per call with x402 means paying for every url you listed: list only the urls you want.",
"It works in chunks of 3 urls, so a failure costs that chunk and not the whole job.",
"No `screenshot` or `pdf` in a batch: every result is kept until you collect it. Ask for those one url at a time."
],
"endpoints": {
"POST /web/v1/scrape/batch": "A batch of scrapes: queues one scrape per url you give it. Same fields as /scrape but with `urls` (2–50) and no `url`. Returns a `jobId`. It discovers nothing — for that, use /crawl.",
"GET /web/v1/scrape/batch/:id": "Collects the job: status, how many are done, and the results so far. `?limit=1..50`.",
"DELETE /web/v1/scrape/batch/:id": "Cancels the job. The urls that never ran are refunded."
}
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.004 USDC on Base to 0x23Fc…Fc75d. The signed payment is good for 5 minutes.
- Paid to
- 0x23Fc…Fc75d
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 4000 smallest units
- Returns
- application/json
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x23Fc725e8EAa1c58900C6507Ba89be99a6DFc75d",
"scheme": "exact",
"network": "eip155:8453",
"mimeType": "application/json",
"resource": "https://api.oassis.dev/web/v1/scrape/batch",
"description": "",
"maxAmountRequired": "4000",
"maxTimeoutSeconds": 300
}
]Provenance
- Seen in the source catalog
- 2026-10-17 13:54Z
- Last indexed by Roundhouse
- 2026-10-18 21:15Z
- Last enriched (probe, favicon, geo)
- 2026-10-07 16:46Z
- x402 version
- 1
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 22 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service api.oassis.dev and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=api.oassis.dev' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.oassis.dev/web/v1/scrape/batch, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.