These terms describe the rules the server applies to every paid call today.
CertBeforePay runs fast, deterministic checks on what your agent sends. A result is a risk signal and a fast deterministic scan, not a guarantee, not a legal PKI, not investment advice, and not a substitute for a human incident response team.
Scan verdicts are ATTEST, CAUTION or HALT. ATTEST means a fixed set of rule checks on the configuration you sent found no high or critical issue. It does not mean the agent was run, tested or audited. A HALT verdict is never hidden, and a certificate from a HALT scan is always provisional.
Certificates are signed scan records, not a legal CA or PKI, and not proof an agent is safe. They expire after 24 hours by default.
The wallet check returns clear, caution or block. It is a scam/phishing signal from the ScamSniffer scam database (GPL-3.0), not an OFAC or sanctions check. It also returns caution when an address starts and ends like a known address but is a different address (address poisoning). It never stops the payment; your agent decides.
Paid routes use x402. The server answers 402 with the price, in USDC on Base (eip155:8453), and your agent retries with a signed payment. There is no account and no API key. Current prices are on the pricing page and at /.well-known/x402.
Prices can change; the price that applies is the one in the 402 your agent signs.
The server checks everything it can before it settles a payment: the payment itself, the wallet proof and your inputs. If one of those checks fails, nothing is charged.
Once a payment has settled, the charge stands and is not refunded, even if the request then fails, except in these server-fault cases. In each one the response says "refund":"pending", and the owner refunds it by hand:
scan_failed with "charged":true: the server faulted after settlement and returned no scan result.store_write_failed: the payment settled, but the server could not save its records.wallet_check_failed: the payment settled, but the server failed to return the wallet-check verdict.self_check_reservation_lost: on certificate issue, the reserved self_check_id could not be marked used, and no certificate was issued.post_settle_error: any other server error after the payment settled.settle_unknown: the settle reply did not say clearly whether the payment was made. The owner checks on-chain and refunds it if it settled.The server holds no wallet keys and never refunds automatically.
On POST /v1/self-check, POST /v1/cert/issue and POST /v1/peer/challenge, a paid call whose subject or payTo is on the scam list is charged and answered 403 scam_wallet_blocked. When the scam list is out of date, a call that checks a wallet address answers 503 scam_denylist_stale and is not charged.
Wallet-check data is derived from the ScamSniffer scam-database, licensed GPL-3.0. Other data and license credits are listed on the home page and in the project NOTICE file.
When a paid route asks you for payment or receives a payment, or when you get a free feed sample, we record the time, route, request method, response status, price quoted or paid, network, the result (payment required, payment failed, blocked before settlement, paid, settlement unknown, refund due, free sample) and its reason code, your payer wallet address when you send a payment, the transaction hash when a payment settles, your user-agent (and the x402 client library it names), and your IP address. We use this only to run, price and improve CertBeforePay, to stop abuse and fraud, and to handle refunds. We keep the raw records for up to 90 days and keep only totals after that. We do not sell or share them. We never record your payment signature, private keys, or the contents of what you submit for checking.
Support: [email protected]
Security reports: [email protected]