x402.deepsense.stream
Developer tools API on Base, paid per request with x402.
- Endpoints9
- Price per requestfrom $0.001
- Outside payers · 7d2
- Answer 402n/a
Overview
- Seller wallet
- 0xd1e706dfbad15cd78053696e67b5c148c2a5cfd5
- Chains
- Base
- Hosts
- x402.deepsense.stream
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Developer tools7Other1Web data1
- First seen
- 2026-10-20 · last seen 2026-10-20
What we observed
Endpoints
EndpointsDescriptions are the seller's own words from the catalogue and are not checked by us. A listed price is a registration, not an observed charge.https://x402.deepsense.stream/api/v1/base64
Encode UTF-8 text to base64 or decode base64 back to UTF-8, with byte counts. Lets an agent move binary-ish payloads through JSON without shipping a codec.
BaseDeveloper tools$0.001/ request
2026-10-19
https://x402.deepsense.stream/api/v1/hash
Hash text with sha256 (default), sha512, sha1 or md5 and get hex plus base64 in one call. Handy for agents that must fingerprint prompts, files or payloads without a local crypto library.
BaseDeveloper tools$0.001/ request
2026-10-19
https://x402.deepsense.stream/api/v1/ping
Zero-dependency health ping for agents: returns ok, service name, ISO timestamp and epoch milliseconds. Use it to verify an x402 client end to end in under a millisecond. No upstream, no storage.
BaseDeveloper tools$0.001/ request
2026-10-19
https://x402.deepsense.stream/api/v1/time
Current time for any IANA timezone (default UTC): ISO 8601, epoch seconds and milliseconds, local wall-clock string, weekday and weekday index, UTC offset in minutes. DST-correct because it uses the system tz database.
BaseDeveloper tools$0.001/ request
2026-10-19
https://x402.deepsense.stream/api/v1/uuid
Cryptographically random UUID v4 identifiers. Ask for 1 to 100 in one paid call. Useful for idempotency keys, request ids, test fixtures and agent-to-agent correlation.
BaseDeveloper tools$0.001/ request
2026-10-19
https://x402.deepsense.stream/api/v1/feedback
Tell us what data or tool you wish existed. Paid structured capability request: use case, missing endpoint, needs, optional contact. Every submission is read; high-demand requests get built and announced.
BaseOther$0.002/ request
2026-10-19
https://x402.deepsense.stream/api/v1/json/repair
Repair almost-JSON produced by LLMs: strips markdown code fences, normalises smart quotes, removes comments and trailing commas, then parses. Returns the parsed value plus the list of repairs applied, or a precise parse…
BaseDeveloper tools$0.002/ request
2026-10-19
https://x402.deepsense.stream/api/v1/json/schema
Infer a JSON Schema (draft 2020-12) from an example JSON value: nested objects, arrays, required keys, integer vs number, and string formats (date, date-time, email, uri, uuid). Useful for tool definitions and structure…
BaseDeveloper tools$0.002/ request
2026-10-19
https://x402.deepsense.stream/api/v1/web/extract
Turn a public web page into an LLM-ready document: clean markdown with nav/cookie/script boilerplate removed, parsed JSON-LD, OpenGraph, heading outline, tables, link graph, word and token counts, and embedding-ready ch…
BaseWeb data$0.005/ request
2026-10-19
Evidence
Answers HTTP 402
Answers HTTP 402Method: one unpaid request per listed endpoint. A 402 with a payment payload a client could parse counts. Nothing is paid.unknown
unknown. We hold no reading for this seller's endpoints.
no reading date
x402-style payments, last 7 days (Base)
x402-style paymentsMethod: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too.2outside payers
20 x402-style payments from 2 distinct payers, $0.05 USDC in the last 7 days (Base, exact read)
window ended 2026-10-20
- Payments
- 20
- Payers
- 2
- USDC
- 0.05
This window shows the pattern of machine noise (few payers, dust amounts), so it does not count toward the evidence ranking.
All USDC received at this payout address: $0.05 (includes payments that are not x402)
Reading: x402-style payments to this payout address on Base, exact read of the 7 days to 2026-10-20, every block of the window: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's `exact` scheme uses. Some non-x402 gasless sends use it too; Sato Hub's own payer wallets are left out
By chain
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0xd1e706dfbad15cd78053696e67b5c148c2a5cfd5 | 9 | unknown | 20 x402-style payments from 2 distinct payers, $0.05 USDC in the last 7 days (Base, exact read) |
One seller wallet, each chain read on its own. We never send a payment, so we never observe what a paid call returns. Unknown means we hold no reading, not that anything failed.
Pricing
The price each endpoint registered in the x402 catalogue. A listed price is a registration, not an observed charge.
Claim this merchant
Sign a message from the payout address 0xd1e706…a5cfd5 to claim this page or download its payment ledger. Claiming proves control of the payout key. It says nothing about the service behind the address, and it does not change how this merchant is ranked. No email, no account: the signature is the whole credential, and signing a message costs no gas and moves nothing.
Data CC-BY-4.0, attribution: data by satohub.ai. Data as of 2026-10-20. Appearing here is not an endorsement. Check an endpoint with the doctor.