75trust / 100

Jpyc Services

by JPYC Service Monitor in Developer tools

x402 APIPassing, checked 1 h ago

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.

GET
https://open-pay.jp/api/paid/usdc/jpyc/services
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
385 ms
625 ms slowest 5%
Last check
Passed
1 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://open-pay.jp/api/paid/usdc/jpyc/services

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://open-pay.jp/api/paid/usdc/jpyc/services?changedSince=2026-08-20

Parameters

ParameterTypeRequiredDescription
changedSincestringNoReturn only changes on/after this date (YYYY-MM-DD). Set to your last run date. Omit for the full snapshot.
limitstringNo1-200 (default 200). In delta mode the limit is rounded up to a date boundary: a single day is never split, so a day holding more events is returned whole. Continue with nextChangedSince while hasMore is true.

Example response

The provider's example. We can't check it without paying.

Example response, 75 lines
{
  "attribution": [
    "JPYC株式会社"
  ],
  "changes": [
    {
      "changeType": "updated",
      "collectedAt": "2026-08-27",
      "date": "2026-05-15",
      "diffs": [
        {
          "currentValue": [
            "avalanche",
            "ethereum",
            "polygon",
            "kaia"
          ],
          "field": "chains",
          "previousValue": [
            "avalanche",
            "ethereum",
            "polygon"
          ]
        },
        {
          "currentValue": "1,000,000 JPY per transaction (issuance)",
          "field": "limit",
          "previousValue": "1,000,000 JPY per day (issuance)"
        }
      ],
      "slug": "jpyc-ex",
      "sourceUrl": "https://prtimes.jp/main/html/rd/p/000000315.000054018.html",
      "summary": "JPYC EX added Kaia support and changed the issuance cap from 1M JPY per day to 1M JPY per transaction.",
      "summaryJa": "JPYC EX が Kaia に対応。発行上限を「1日100万円」から「1回100万円」へ変更。"
    }
  ],
  "generatedAt": "2026-08-27T01:23:45.000Z",
  "hasMore": false,
  "licenseNotice": "Facts summarized from official sources; source rights remain with their owners.",
  "mode": "delta",
  "nextChangedSince": "2026-08-27",
  "notice": {
    "code": "sourced-facts-only",
    "detail": "Change events and rows summarize what official sources state; they are not availability guarantees or endorsements.",
    "termsUrl": "https://open-pay.jp/en/terms"
  },
  "query": {
    "changedSince": "2026-05-15",
    "limit": 200
  },
  "schemaVersion": "1.0",
  "services": [
    {
      "category": "exchange",
      "chains": [
        "avalanche",
        "ethereum",
        "kaia",
        "polygon"
      ],
      "name": "JPYC EX",
      "nameJa": "JPYC EX",
      "slug": "jpyc-ex",
      "sourceCheckedAt": "2026-08-27T01:00:00.000Z",
      "sourceOk": true,
      "sourceUrl": "https://jpyc.co.jp/",
      "status": "published",
      "supportsJpyc": true,
      "supportsUsdc": false,
      "supportsX402": false,
      "verifiedAt": "2026-08-27"
    }
  ],
  "totalServices": 20
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://open-pay.jp/api/paid/usdc/jpyc/services?changedSince=2026-08-20'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://open-pay.jp/api/paid/usdc/jpyc/services?changedSince=2026-08-20' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fopen-pay.jp%2Fapi%2Fpaid%2Fusdc%2Fjpyc%2Fservices
const res = await pay("https://open-pay.jp/api/paid/usdc/jpyc/services?changedSince=2026-08-20");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://open-pay.jp/api/paid/usdc/jpyc/services?changedSince=2026-08-20")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
1 h agoPassed402345 ms$0.01
6 h agoPassed402368 ms$0.01
11 h agoPassed402467 ms$0.01
15 h agoPassed402361 ms$0.01
20 h agoPassed402464 ms$0.01
Show 10 older checks
25 h agoPassed402378 ms$0.01
29 h agoPassed402415 ms$0.01
33 h agoPassed402435 ms$0.01
37 h agoPassed402431 ms$0.01
42 h agoPassed402408 ms$0.01
46 h agoPassed402536 ms$0.01
2 days agoPassed402375 ms$0.01
2 days agoPassed402384 ms$0.01
2 days agoPassed402429 ms$0.01
3 days agoPassed402443 ms$0.01