Sato Hub
x402 merchant

api.jpverify.com

Developer tools API on Base, paid per request with x402.

  • Endpoints7
  • Price per requestfrom $0.001
  • Outside payers · 7d1
  • Answer 4020 of 2

Overview

as of 2026-10-08
Seller wallet
0xe4a4e5b226be71e7b6ed523bc7a91089c770572f
Chains
Base
Hosts
api.jpverify.com
CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
Developer tools2Identity2Other2Market data1
First seen
2026-10-05 · last seen 2026-10-08

What we observed

Paid by 1 outside payer · 7d, observedNo 402 answer, not observedNot claimed
See the readings

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.
7 registered

  • https://api.jpverify.com/jp-address/postal-lookup

    Japanese postal-code lookup and reverse lookup. Keywords: Japanese postal lookup, Japan Post postal code, postal code reverse lookup, 日本郵便番号検索. Use a postal code or prefecture/city/ward/town components against the local…

    BaseOther

    $0.001/ request

    2026-09-17

  • https://api.jpverify.com/jp-address/geocode

    Japanese forward geocoding from an address to coordinates. Keywords: Japan geocoder, address to coordinates, building-level geocode, Jageocoder, chome, block, lot, house. Returns provider-neutral local candidates, coord…

    BaseOther

    $0.005/ request

    2026-09-10

  • https://api.jpverify.com/jp-address/parse

    Japanese address parser and component extraction. Keywords: Japanese address parser, address components, chome, block, lot, house, 丁目, 番地, 号. Parse a Japanese address into components without returning postal validation …

    BaseDeveloper tools

    $0.005/ request

    2026-09-14

  • https://api.jpverify.com/jp-address/validate

    Japanese address validation and quality decision. Keywords: Japanese address validation, address conflict, address quality, partial match, 日本住所検証. Validate parser, postal, and geocoder evidence using one address policy,…

    BaseDeveloper tools

    $0.005/ request

    2026-09-10

  • https://api.jpverify.com/v1/entities/resolve-cross-border

    Resolve a JP or GB entity using projected official evidence from NTA/gBizINFO or Companies House; raw upstream responses are not returned. Hard identity conflicts are never verified. / 日本または英国の企業を公式根拠の加工済み投影で確認します。元データは…

    BaseIdentity

    $0.04/ request

    2026-10-08

  • https://api.jpverify.com/v1/entities/:entity_id/filing-risk-snapshot

    Return objective SEC EDGAR filing and disclosure metadata for a known CIK. This is not a credit rating or investment advice; results are cached and globally rate limited. / 既知のCIKについてSEC EDGAR提出書類と開示メタデータを返します。信用格付けや投資助…

    BaseMarket data

    $0.05/ request

    2026-09-10

  • https://api.jpverify.com/v1/invoices/counterparty-check

    Check a known EU VAT ID and/or Peppol participant using separate tax-validity, entity-match, and discoverability evidence. VIES is never used for name search and upstream responses are not resold. / 既知のEU VAT IDまたはPeppo…

    BaseIdentity

    $0.05/ request

    2026-10-08

Evidence

as of 2026-10-08

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.

0 of 2

0 of 2 probed endpoints answered HTTP 402 with a parseable payment payload

checked 2026-09-21

x402-style payments, last 7 days (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.

1outside payer

2 x402-style payments from 1 distinct payer, $0.09 USDC in the last 7 days (Base, exact read)

window ended 2026-10-08

Payments
2
Payers
1
USDC
0.09

All USDC received at this payout address: $0.09 (includes payments that are not x402)

Reading: x402-style payments to this payout address on Base, exact read of the 7 days to 2026-10-08, every block of the window: 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; Sato Hub's own payer wallets are left out

By chain

ChainSeller walletEndpointsAnswers 402x402-style payments
Base0xe4a4e5b226be71e7b6ed523bc7a91089c770572f70 of 2 probed endpoints answered HTTP 402 with a parseable payment payload
2026-09-21
2 x402-style payments from 1 distinct payer, $0.09 USDC in the last 7 days (Base, exact 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

Lowest
$0.001
per request, as registeredas of
Median
$0.005
per request, as registeredas of
Highest
$0.05
per request, as registeredas of

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 0xe4a4e5…70572f 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 as of 2026-10-08. Appearing here is not an endorsement. Check an endpoint with the doctor.