open-pay.jp
https://open-pay.jp/api/paid/usdc/jpyc/servicesShares a payout wallet with 12 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
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.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 66ms · p95 144msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 8/27/2026, 12:00:00 AM | 100% | 13 | 67ms |
| 8/28/2026, 12:00:00 AM | 100% | 21 | 66ms |
| 8/29/2026, 12:00:00 AM | 100% | 3 | 55ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 36
- Activity
- 4
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 74% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 8/28/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 8/2/2026 | 1 | 0.01 | 1 |
| 8/3/2026 | 1 | 0.01 | 1 |
| 8/17/2026 | 1 | 0.01 | 1 |
| 8/18/2026 | 1 | 0.01 | 1 |
| 8/19/2026 | 1 | 0.01 | 1 |
| 8/20/2026 | 2 | 0.02 | 1 |
| 8/21/2026 | 7 | 0.11 | 1 |
| 8/23/2026 | 8 | 0.04 | 2 |
| 8/25/2026 | 1 | 0.01 | 1 |
| 8/26/2026 | 2 | 0.02 | 1 |
| 8/27/2026 | 2 | 0.02 | 1 |
| 8/28/2026 | 1 | 0.01 | 1 |
This payout wallet is shared: figures cover all 13 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.