Call FOXIFY from your own agent. Nothing runs from Fox's laptop.
The customer runtime is hosted on FOXIFY's Cloudflare and Supabase surfaces. The private Lab is only for engineering and acceptance tests.
Payment-intent preflight · $0.05 USDC
LIVE · 402 challenge verified now
Observed 2026-09-30T18:30:16.707Z
- POST https://x402.foxify.pro/preflight
- Network: Base eip155:8453
- Native USDC: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
- Exact price: 0.05 USDC (50000 atomic)
- An unpaid call returns HTTP 402 plus the machine-readable payment contract.
- A compatible x402 client validates the quote, signs in its own wallet, retries once, then receives ALLOW / REVIEW / DENY evidence.
curl -i -X POST https://x402.foxify.pro/preflight \
-H 'content-type: application/json' \
--data '{}'The empty request above is an unpaid discovery probe. It does not sign or spend anything.
Exact action-authority preflight · $0.25 USDC
For consequential actions, send the actual subject, tool, operation, exact target, canonical parameters, authority lifetime, retry state and required postcondition.
POST https://xqmokxkbgewocuiinnot.supabase.co/functions/v1/foxify-agent-action-preflight-paid
A valid action payload is required before this route can reach its payment challenge.
Remote MCP
- Registry: io.github.speeedy10/foxify-x402-agent-commerce-payment-preflight
- Streamable HTTP: https://xqmokxkbgewocuiinnot.supabase.co/functions/v1/foxify-agent-commerce-mcp
- Free tool: foxify_preflight_info
- Paid tools: verify_agent_payment_intent and verify_agent_action_intent
Production payment flow
- Send the intended request and read the 402 terms.
- Verify Base, native USDC, amount and recipient before signing.
- Sign with the caller's own wallet or x402 client. FOXIFY never needs the seed phrase or private key.
- Retry the same request once with the payment envelope.
- Persist result and settlement evidence. If the outcome is ambiguous, reconcile it; do not create a second payment.
Public discovery
The payment-intent service is online and payment-ready on x402-list. Its public directory page is independently monitored; no on-chain settlement is claimed until one is actually observed.