Verify that your agent's work actually happened, with signed proof. One paid call per check returns a pass/fail verdict plus Ed25519-signed evidence you can hand to a human. Use it to: check if a website or link is up (status, redirects, TLS/SSL certificate, latency, uptime check); verify an email was delivered and test email deliverability (catch-all test inbox with SPF, DKIM and DMARC alignment and raw headers, for signup, password-reset and cold-email checks); test that a webhook fired (Stripe, GitHub or any webhook receiver URL, also a cron job heartbeat); look up DNS records (TXT, MX, SPF, DKIM, DMARC, CNAME); render a JavaScript page in a real headless browser, assert text or a CSS selector, and get a screenshot. Pay per call in USDC on Base via x402, no API key or account. Failed checks are never charged.
https://router.fluxapay.xyz/api/proofwire-verification-api/{CREATOR_UID}DNS lookup and email-auth setup check: resolve A, AAAA, CNAME, MX, TXT, NS and CAA records from public resolvers (not a cache), with parsed SPF, DMARC policy and DKIM key for a selector. Use to verify a domain, MX or SPF/DKIM/DMARC configuration after setup, or to confirm a DNS change propagated. Optional expect asserts a value appears. Ed25519-signed evidence.
Did the email actually arrive? Watches a test inbox for a time window (polls inside the paid window are free) and returns delivered or not, received-at time, and email authentication results: SPF, DKIM and DMARC pass/fail with alignment, ARC, a heuristic spam-risk score, and the raw headers as evidence. Use for email deliverability tests, verifying signup and password-reset emails, and checking DKIM/SPF setup. Ed25519-signed.
Create a disposable test email inbox (catch-all seed address) for email delivery testing. Give the address to whatever sends mail (signup, password reset, magic link, CRM or cold-email campaign), then call GET /v1/verify/email with the returned inbox and token to confirm delivery and authentication. Valid up to 72 hours.
Check if a website or URL is up and working: real HTTP fetch following redirects. Returns pass/fail verdict, final URL, status code, latency, full redirect chain, TLS/SSL certificate validity and days to expiry, and a SHA-256 hash of the body, all Ed25519-signed. Use to verify a link before sharing it, uptime and health checks, or broken-link detection. Params: url (required), expect_status (e.g. 200).
Does the page really show it? Render a URL in a real headless Chromium browser (JavaScript, network, SPA), wait, then assert a CSS selector and/or visible text. Returns pass/fail, extracted text, page title, console errors, failed requests and a screenshot URL. Use to verify a deploy, check what a JavaScript site actually displays, scrape rendered text, or capture a screenshot as proof. Timeouts on our side are never charged.
Webhook tester and receiver: arm a one-time tripwire URL that records every request (payload, headers, source IP) for up to an hour. Register it as the webhook target in Stripe, GitHub, Shopify or any system to prove the event fired, or ping it from a cron job as a heartbeat (expect_by flags a missed deadline). Poll GET /v1/verify/webhook/{id}?token= for free during the window.
Copy this prompt and paste it into your AI agent (like Claude, GPT-4, etc.) to enable automatic X-402 payment handling.
** Your task ** Call the API at: https://router.fluxapay.xyz/api/proofwire-verification-api/{CREATOR_UID}
Follow the steps below in order.
** Step 1 - Install FluxA Wallet CLI **
npm install -g @fluxa-pay/fluxa-wallet
Or use without installing: npx fluxa-wallet <command>
** Step 2 - Register agent **
fluxa-wallet init --name "<YOUR_AGENT_NAME>" --client "<YOUR_CLIENT>"
The response may include an authorization URL. Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<URL>"' to open in their browser.
Verify: fluxa-wallet status
** Step 3 - Discover endpoints **
curl https://router.fluxapay.xyz/api/proofwire-verification-api/{CREATOR_UID}
Returns JSON with: name, description, endpoints (paths, methods, descriptions, prices), paymentRequired, and networks.
** Step 4 - Choose payment method **
Ask the user: [On-chain USDC (Base)] or [FluxA Monetize Credits]
If USDC:
- --currency USDC
- --amount in atomic units (6 decimals, e.g., 100000 = 0.10 USDC)
If Credits (1 credit = 1 USDC):
- --currency FLUXA_MONETIZE_CREDITS
- --amount in 2-decimal units (e.g., 10 = 0.10 credits, 100 = 1.00 credits)
** Step 5 - Create an intent mandate **
x402 v3 uses intent mandates: the user pre-approves a spending plan (budget + time window), then the agent makes autonomous payments within those limits.
fluxa-wallet mandate-create \
--desc "Spend up to <BUDGET> for <DESCRIPTION> valid for <DURATION>" \
--amount <BUDGET_IN_UNITS> \
--seconds <DURATION_IN_SECONDS> \
--currency <USDC or FLUXA_MONETIZE_CREDITS>
Options:
- --desc (required): Human-readable spending plan description
- --amount (required): Budget in units for the chosen currency (see Step 4)
- --seconds (optional, default 28800 = 8h): Duration in seconds
- --currency (optional, default USDC): USDC or FLUXA_MONETIZE_CREDITS
** Step 6 - Get user to sign the mandate **
The response from Step 5 includes mandateId and authorizationUrl (TTL: 10 minutes).
Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<authorizationUrl>"' to open in their browser.
** Step 7 - Wait for mandate to be signed **
fluxa-wallet mandate-status --id <MANDATE_ID>
Poll until mandate.status is "signed". The response also includes remainingAmount.
Important: Use --id, not --mandate.
** Step 8 - Call the API **
curl https://router.fluxapay.xyz/api/proofwire-verification-api/{CREATOR_UID}
Optionally add the X-Agent-ID header for agent attribution (its value is the agent_id from 'fluxa-wallet status'): curl -H "X-Agent-ID: <YOUR_AGENT_ID>" https://router.fluxapay.xyz/api/proofwire-verification-api/{CREATOR_UID}
If it returns HTTP 402, continue to Step 9.
** Step 9 - Pay via x402 v3 **
Pass the complete HTTP 402 response body as --payload:
fluxa-wallet x402-v3 \
--mandate <MANDATE_ID> \
--payload '$PAYLOAD_402'
The payload must contain an accepts array. Do NOT extract individual fields - pass the entire 402 response JSON.
The response includes xPaymentB64 (the payment token).
** Step 10 - Retry with payment token **
Retry the same request with the X-Payment header (optionally add X-Agent-ID for attribution):
curl -H "X-Payment: <xPaymentB64>" <ORIGINAL_API_URL>
Return the raw API response to the user without post-processing.
** Opening links for user **
Whenever you need to open a URL (authorization, approval, or any external link):
1. Present the user with a choice using your interactive options/menu capability (e.g., AskUserQuestion tool)
2. Options: [Yes, open the link] [No, don't open]
3. If YES: run 'open "<URL>"' to open in their default browser
4. If NO: ask how they would like to proceed
** Error handling **
- mandate_not_signed: User hasn't signed yet - ask them to open authorizationUrl
- mandate_expired: Time window passed - create a new mandate
- mandate_budget_exceeded: Budget too low - create a new mandate with a higher limit
- agent_not_registered: No Agent ID - run 'fluxa-wallet init' first
- Invalid payload: missing accepts array: Pass the full 402 response JSON