TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-28 · finished 2026-10-28 13:07 UTC
Listed
32,435

jpyc services derived

open-pay.jpIdentityderived

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

passlisted in Coinbase#4 by calls of 4 on this host

0.01 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-13 14:08 UTC · method · pinnable

Validation state
pass
as of 2026-10-28 09:29 UTC · method · pinnable · sweep daily-2026-10-28
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-28 09:29 UTC · method · pinnable · 4 of 4 in 7d, 17 of 17 in 30d, 30 of 30 in 90d
Calls, trailing 30 days
1
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-09 05:53 UTC
as of 2026-10-13 14:08 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.01 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
2
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

80 observations, 2 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 2,150 endpoints in Identity that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 1,412 in the category are counted higher and 737 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 80 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.

In words

At open-pay.jp, jpyc services takes GET requests, is listed in the Coinbase registry, and falls under identity by TOLL's rules.

On Base, jpyc services asks 0.01 USDC per call.

Requests carry the query parameter changedSince.

jpyc services accepts payment on Base and EVM chain 5042, 2 options in all, all to one wallet.

A response from jpyc services, as declared, includes mode, query, notice, changes, hasMore, services and 2 others.

jpyc services answered the sweep of 2026-10-28 with a valid 402, as at every sweep since 2026-09-11.

Of open-pay.jp's 4 listings, jpyc services ranks 4th by calls.

It accounts for 5% of the calls counted across the host.

jpyc services drew a single call from a single payer in the trailing 30 days.

The last call to jpyc services came 4 days before the snapshot, 2026-10-09.

Closest in price to jpyc services within identity: screening match at api.relaystation.ai and icypeas result at vaaya.ai.

jpyc services is priced above 34% of comparable listings in identity.

The wallet paid by jpyc services is the payee of 12 endpoints across 2 hosts.

For 1 of the options on jpyc services, TOLL has no verified decimals and shows the raw amount.

The seller's tags on jpyc services are jpyc, japan, web3 and monitoring.

jpyc services dropped out of the registry at the pull of 2026-09-26 and was listed again on 2026-10-09.

The price of jpyc services is declared by 707 other listings in identity too.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.01 USDCexact0x52d490…a3cA81
Coinbaseeip155:5042GatewayWalletBatched10000 smallest units, decimals unknownexact0x52d490…a3cA81

Preflight checks at the last sweep

the checks, as of 2026-10-28 09:29 UTC · method · pinnableendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-28 09:29 UTCpass0daily-2026-10-28
2026-10-27 09:12 UTCpass0daily-2026-10-27
2026-10-26 15:40 UTCpass0daily-2026-10-26
2026-10-23 09:25 UTCpass0daily-2026-10-23
2026-10-21 11:55 UTCpass0daily-2026-10-21
2026-10-20 11:33 UTCpass0daily-2026-10-20
2026-10-19 09:12 UTCpass0daily-2026-10-19
2026-10-18 11:03 UTCpass0daily-2026-10-18
2026-10-17 21:28 UTCpass0daily-2026-10-17
2026-10-16 07:14 UTCpass0daily-2026-10-16
2026-10-15 09:02 UTCpass0daily-2026-10-15
2026-10-14 07:03 UTCpass0daily-2026-10-14
2026-10-13 11:49 UTCpass0daily-2026-10-13
2026-10-12 09:09 UTCpass0daily-2026-10-12
2026-10-11 07:52 UTCpass0daily-2026-10-11
2026-10-10 16:00 UTCpass0daily-2026-10-10
2026-10-09 13:43 UTCpass0daily-2026-10-09
2026-09-25 21:21 UTCpass0daily-2026-09-25
2026-09-23 06:54 UTCpass0daily-2026-09-23
2026-09-22 07:07 UTCpass0daily-2026-09-22
2026-09-21 07:29 UTCpass0daily-2026-09-21
2026-09-19 05:31 UTCpass0daily-2026-09-19
2026-09-18 13:57 UTCpass0daily-2026-09-18
2026-09-17 05:24 UTCpass0daily-2026-09-17
2026-09-16 05:23 UTCpass0daily-2026-09-16
2026-09-15 05:40 UTCpass0daily-2026-09-15
2026-09-14 05:13 UTCpass0daily-2026-09-14
2026-09-13 05:09 UTCpass0daily-2026-09-13
2026-09-12 07:26 UTCpass0daily-2026-09-12
2026-09-11 11:10 UTCpass0daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. back in Coinbase
  2. absence from Coinbase confirmed, rule v1
  3. absent from Coinbase at this pull
  4. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-09 05:53 UTC · method · live

The input and output block
{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "changedSince": "2026-08-20"
    }
  },
  "output": {
    "type": "json",
    "example": {
      "mode": "delta",
      "query": {
        "limit": 200,
        "changedSince": "2026-05-15"
      },
      "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"
      },
      "changes": [
        {
          "date": "2026-05-15",
          "slug": "jpyc-ex",
          "diffs": [
            {
              "field": "chains",
              "currentValue": [
                "avalanche",
                "ethereum",
                "polygon",
                "kaia"
              ],
              "previousValue": [
                "avalanche",
                "ethereum",
                "polygon"
              ]
            },
            {
              "field": "limit",
              "currentValue": "1,000,000 JPY per transaction (issuance)",
              "previousValue": "1,000,000 JPY per day (issuance)"
            }
          ],
          "summary": "JPYC EX added Kaia support and changed the issuance cap from 1M JPY per day to 1M JPY per transaction.",
          "sourceUrl": "https://prtimes.jp/main/html/rd/p/000000315.000054018.html",
          "summaryJa": "JPYC EX が Kaia に対応。発行上限を「1日100万円」から「1回100万円」へ変更。",
          "changeType": "updated",
          "collectedAt": "2026-08-27"
        }
      ],
      "hasMore": false,
      "services": [
        {
          "name": "JPYC EX",
          "slug": "jpyc-ex",
          "chains": [
            "avalanche",
            "ethereum",
            "kaia",
            "polygon"
          ],
          "nameJa": "JPYC EX",
          "status": "published",
          "category": "exchange",
          "sourceOk": true,
          "sourceUrl": "https://jpyc.co.jp/",
          "verifiedAt": "2026-08-27",
          "supportsJpyc": true,
          "supportsUsdc": false,
          "supportsX402": false,
          "sourceCheckedAt": "2026-08-27T01:00:00.000Z"
        }
      ],
      "attribution": [
        "JPYC株式会社"
      ],
      "generatedAt": "2026-08-27T01:23:45.000Z",
      "licenseNotice": "Facts summarized from official sources; source rights remain with their owners.",
      "schemaVersion": "1.0",
      "totalServices": 20,
      "nextChangedSince": "2026-08-27"
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "jpyc services on open-pay.jp", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/open-pay-jp-api-paid-usdc-jpyc-services-8196df/at/2026-10-13T14-08Z. Accessed [access date].

BibTeX

@misc{toll-e-open-pay-jp-api-paid-usdc-jpyc-services-8196df-2026-10-13T14-08Z,
  author = {TOLL},
  title = {jpyc services on open-pay.jp},
  howpublished = {\url{https://tollindex.com/e/open-pay-jp-api-paid-usdc-jpyc-services-8196df/at/2026-10-13T14-08Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about jpyc services, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 8196df3cd0b37d7f83b64630a3189495c5c6a34e5afaa0c48c84164b33b86d29 from wallet 0x52d4901142e2B5680027da5EB47C86CB02a3cA81

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.