OpenPay Discovery, Directory and Shops APIs
activePayable x402 resources, structured Japan Web3 directory data, and opt-in JPYC shop discovery.
Settled via Coinbase.
- Transactions · 30d
- 0
- Volume · 30d
- $0.00
- Unique buyers · 30d
- 0
- Uptime · 30d
- 100.0%
- Latency p50
- 136ms
- Reported calls · 30d
- 26
Endpoints (19 live)
GET/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. (1000 on Base)GET/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 bucket; exact block and time range are in the response. Use for current JPYC usage metrics; not for wallet balances, price, news, supply or financial advice. (0.01 USDC on Base)GET/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, categorized and tied to an official source URL. Pass changedSince=YYYY-MM-DD (your last run date) to fetch only new events; an empty changes list explicitly means no change. Without changedSince you get the full dated history back to late 2025. (0.01 USDC on Base)GET/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 set to your last run date to fetch only what changed; an empty changes list explicitly means no change, so a scheduled agent can report that without guessing. Without changedSince you get the full monitor snapshot. (0.01 USDC on Base)GET/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 payment, for treasury checks, wallet monitoring, and payment reconciliation. The result does not prove wallet ownership and is not a transaction-finality certificate. (0.002 USDC on Base)GET/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 comparison, or verifying a current JPYC supply figure before citing it. Not for market price, reserve backing, circulating-supply analysis, or financial advice. (0.002 USDC on Base)GET/api/paid/usdc/jpyc/transfers— List recent JPYC Transfer events on one supported chain from roughly the last hour of blocks, optionally filtered by address — tx hash, from, to, amount, block. Without a cursor: newest first. With a cursor: only events after that position, oldest first, so each observed event is returned once within the scanned window. Use to confirm a recent JPYC payment or monitor wallet activity. Not for history beyond the window, sanctions screening, identity, or finality proof. (0.005 USDC on Base)GET/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. (0.02 USDC on Base)GET/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. (0.04 USDC on Base)GET/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. (0.02 USDC on Base)GET/api/paid/usdc/jpyc/attest— Signed record of the JPYC transfers in one transaction, read from public RPC at request time, with amounts, totals, block timestamp and finality observations. Use for payment reconciliation and retaining a machine-readable record. The signature shows only that OpenPay observed these on-chain facts at the stated time; it is not a legal certification. (0.1 USDC on Base)GET/api/paid/usdc/japan-web3-directory/licensed— 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. Includes a commercial-use license (attribution required) and an EIP-712 attestation binding the buyer address, content hash and issue time. (1 USDC on Base)GET/api/paid/stablecoin-payments(free)GET/api/paid/jpyc/services(free)GET/api/paid/japan-web3-directory(free)GET/api/paid/jpyc-shops/search(free)GET/api/paid/demo(free)GET/api/paid/japan-web3-directory/search(free)GET/api/paid/stores(free)
First seen · last seen · last active