Safe inputs
- public HTTPS target URL
- expected service, endpoint, protocol, price, network, asset, or public pay-to facts
- public HTTP 402 challenge metadata
- observed response status and selected public headers
Agent task · pre-payment identity check
Know who your agent is paying before money moves.
Use PayeeProof immediately before an autonomous machine payment when endpoint identity and public payment destination consistency matter. The completed specialist check costs exactly $0.01 USD on compatible stablecoin machine-payment rails.
Workflow
Six steps, with the spending decision left to the caller.
Discover the target serviceResolve the public endpoint and obtain its machine-payment metadata or HTTP 402 challenge.
Supply safe evidenceFor GET or HEAD, PayeeProof can perform a bounded anonymous HTTPS probe. For POST, PUT, PATCH, or DELETE, supply the already-observed 402 response metadata.
Call the specialistInvoke payeeproof.check_payee or POST /v1/payee/check.
Pass eligibility before paymentUnsafe, unsupported, or insufficient requests are rejected before a PayeeProof payment challenge. Eligible requests receive the exact $0.01 stablecoin challenge.
Read the settled resultAfter settlement, inspect assessment, individual checks, provenance, continuity, limitations, recommended machine next step, and deterministic digest.
Apply your own spending policyA consistent result means the available public facts agree. It is not authorization to pay the target.
Payment behavior
One cent. Stablecoin rails only.
HTTP can challenge over MPP/Tempo and x402 when configured. MCP uses MPP/Tempo. PayeeProof does not offer an ordinary Stripe card or payment-link fallback for this operation.
Operationpayeeproof.check_payee
Price$0.01 USD exactly
HTTP routePOST /v1/payee/check
Live target probesGET / HEAD only
State-changing targetscaller-observed 402 required
Credential forwardingnever
Never send
Keep target credentials out of PayeeProof.
Do not send the target merchant's payment credential, private key, bearer token, Authorization header, cookie, card data, or arbitrary private request body. PayeeProof does not need them and will not forward them.
Bounded output
- consistent, review_required, or conflict
- individual pass, warn, fail, or unknown checks
- provenance, continuity, limitations, and next-step signal
- deterministic SHA-256 digest
Integrate against the machine contract.
The discovery surfaces expose the same one-cent operation and the same conservative trust boundary.