- Pricing and payment terms
- Compare whether price, amount, and refund or rate-limit caveats are public, returned by the 402 challenge, or still endpoint-specific.
- Chain, currency, and asset support
- Check public support for networks and payment assets such as Base or USDC instead of assuming all wallets, chains, or currencies are accepted.
- Request signing and 402 flow
- Look for the first 402 challenge, payment-required header or body, payment signature step, and final 200 data response before calling a source machine-payable.
- Endpoint coverage
- Distinguish x402-enabled quote, listing, DEX, or marketplace endpoints from the broader provider catalog and from non-x402 market-data or on-chain-state sources.
- Human and agent callability
- Prefer evidence that says whether developers, backend systems, wallets, or AI agents can call the endpoint and what spending controls are expected.
- PubFi payment boundary
- Use this page for source discovery and integration interest; it does not claim PubFi executes x402 supplier payments or exposes a payment route today.