open-pay.jp
Onchain data API on Base, paid per request with x402.
- Endpoints11
- Price per requestfrom $0.001
- Outside payers · 7dn/a
- Answer 4023 of 3
Overview
- Seller wallet
- 0x52d4901142e2b5680027da5eb47c86cb02a3ca81
- Chains
- Base
- Hosts
- getbits.net, open-pay.jp
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Onchain data6Developer tools3Other1Security1
- First seen
- 2026-10-05 · last seen 2026-11-20
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://open-pay.jp/api/paid/hello
End-to-end smoke test for x402 clients: returns a greeting plus the settlement timestamp, so an agent can prove its payment path works before spending on real data.
BaseDeveloper tools$0.001/ request
2026-11-19
https://open-pay.jp/api/paid/usdc/jpyc/balance
Read the current on-chain JPYC balance of any EVM address on one or all supported chains (Polygon, Kaia, Avalanche, Ethereum), with the token contract and the block number observed at request time. Use before or after a…
BaseOnchain data$0.002/ request
2026-11-20
https://open-pay.jp/api/paid/usdc/jpyc/supply
Read the current contract-reported JPYC totalSupply on Polygon, Kaia, Avalanche or Ethereum, with the token contract address and the block number observed at request time. Use for periodic supply monitoring, cross-chain…
BaseOnchain data$0.002/ request
2026-11-02
https://open-pay.jp/api/paid/usdc/jpyc/transfers
Recent JPYC Transfer events in a roughly one-hour window ending at head - depth (64 blocks on Polygon/Ethereum; 2 blocks on Kaia/Avalanche), with optional address filtering. Use for delayed transfer or wallet monitoring…
BaseSecurity$0.005/ request
2026-11-20
https://aegis-ai.xyz/api/d2a/briefing-jpyc
Aegis - Cut Through the Noise in Your Feeds. ブリーフィング トップ3
BaseOther$0.006/ request
2026-11-02
https://aegis-ai.xyz/api/d2a/briefing
Aegis curated briefing — AI-scored content feed with V/C/L metrics
BaseOther$0.01/ request
2026-10-08
https://open-pay.jp/api/paid/usdc/jpyc/activity
JPYC transfer metrics computed hourly from finalized Polygon blocks: event count, unique senders and receivers, volume, median and top receivers. Covers approximately 24 hours ending at the newest finalized hourly bucke…
BaseOther$0.01/ request
2026-10-27
https://open-pay.jp/api/paid/usdc/jpyc/services
JPYC Service Monitor: weekly change feed for Japan-related JPYC and Web3 services. Each event is dated, typed (added / updated / removed / verified) and tied to an official source URL. Call with changedSince=YYYY-MM-DD …
BaseDeveloper tools$0.01/ request
2026-11-20
https://open-pay.jp/api/paid/usdc/stablecoin-payments
Japan Stablecoin Payment Monitor: weekly change feed for stablecoin payment services in Japan — new launches, pilots, partnerships, fee changes, supported assets and chains, and closures. Each event is dated, categorize…
BaseOnchain data$0.01/ request
2026-11-16
https://getbits.net/v1/events
Japanese crypto exchange listing and delisting events as English JSON.
BaseDeveloper tools$0.02/ request
2026-10-26
https://open-pay.jp/api/paid/usdc/japan-web3-directory
Japan Web3 Directory, full export: sourced records on Japan's JPYC/USDC, exchange, wallet and AI-agent services — every row carries an official source URL and last-verified date.
BaseOnchain data$0.02/ request
2026-11-20
https://open-pay.jp/api/paid/usdc/japan-web3-directory/search
Filter the Japan Web3 Directory by category, token, chain or capability — the same sourced, date-stamped records as the full export, without pulling rows your agent doesn't need.
BaseOnchain data$0.02/ request
2026-11-20
https://open-pay.jp/api/paid/usdc/stores
Where JPYC (Japan's yen-pegged stablecoin) is accepted: curated exchanges, DEXes, dApps and bridges as JSON, each with category, supported assets and an official URL.
BaseOnchain data$0.04/ request
2026-11-20
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.3 of 3
3 of 3 probed endpoints answered HTTP 402 with a parseable payment payload
checked 2026-11-12
x402-style payments, 7-day window (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.unknown
unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks read))
window ended 2026-11-19
By chain
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0x52d4901142e2b5680027da5eb47c86cb02a3ca81 | 11 | 3 of 3 probed endpoints answered HTTP 402 with a parseable payment payload 2026-11-12 | unknown. the 7-day payments read on Base did not complete (time budget spent at block 58811722 (574000 of 3024001 blocks 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 0x52d490…a3ca81 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: x402-list.com (CC BY 4.0). Data as of 2026-11-20. Appearing here is not an endorsement. Check an endpoint with the doctor.