api.payperscreen.com
Security API on Base, paid per request with x402.
- Endpoints5
- Price per requestfrom $0.01
- Outside payers · 7d1
- Answer 402n/a
Overview
- Seller wallet
- 0xa816343b4f88742faef03f51ec23eee1367c6f76
- Chains
- Base
- Hosts
- api.payperscreen.com
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Security4Other1
- First seen
- 2026-10-13 · last seen 2026-10-13
What we observed
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.https://api.payperscreen.com/screen-ip
IP risk check (beta)
BaseSecurity$0.01/ request
2026-10-12
https://api.payperscreen.com/screen
Sanctions screening
BaseSecurity$0.02/ request
2026-10-12
https://api.payperscreen.com/screen-address
Crypto address screening: OFAC sanctions, stablecoin freezes and known hack proceeds
BaseSecurity$0.02/ request
2026-10-12
https://api.payperscreen.com/screen-email
Email trust check
BaseSecurity$0.02/ request
2026-10-12
https://api.payperscreen.com/context
Field comparison
BaseOther$0.05/ request
2026-10-12
Evidence
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.unknown
unknown. We hold no reading for this seller's endpoints.
no reading date
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
9 x402-style payments from 1 distinct payer, $0.38 USDC in the last 7 days (Base, exact read)
window ended 2026-10-13
- Payments
- 9
- Payers
- 1
- USDC
- 0.38
All USDC received at this payout address: $0.38 (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-13, 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
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0xa816343b4f88742faef03f51ec23eee1367c6f76 | 5 | unknown | 9 x402-style payments from 1 distinct payer, $0.38 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
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 0xa81634…7c6f76 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-13. Appearing here is not an endorsement. Check an endpoint with the doctor.