Verification for api.warppay402.com

✓ 1. Claim ✓ 2. Email confirmed ✓ 3. Domain file seen ✓ 4. Verified
✓Publish the verification file▾
Create /.well-known/x402-trust.txt on api.warppay402.com with exactly this content:
last successful file check 2026-10-02 21:39 UTC
✓Confirm your email▾
Status: confirmed (warppay.402@gmail.com). The address is published as the provider contact while the verification is active.

Your public profile

Organization: WarpPay402
Support: https://www.warppay402.com/support
Docs: https://docs.warppay402.com/
Description: MCP Server with LangChain, llms.txt, well-known-JSON, and OpenAI specs currently hosting 21 tools (from web-scraper to BASE, SOLANA, and ARC Smart Contract Factories). Current plugins for Python, Claude, and OpenClaw.
Provider alerts: enabled
Endpoints covered by this host: /api/v1/telemetry/settlements, /api/v1/tools/web-scraper, /api/v1/tools/arc-dex-oracle, /api/v1/tools/aerodrome-swap, /api/v1/tools/aerodrome-clamm, /api/v1/tools/aerodrome-veaero, /api/v1/tools/browser-scraper, /api/v1/tools/arc-analytics, /public_data_feed/%7Bfilename%7D, /api/v1/tools/deploy-contract, /api/v1/tools/deploy-solana-contract, /api/v1/tools/arc-network-query, /api/v1/feeds/%7BfeedId%7D, /api/v1/tools/aerodrome-yields, /public_data_feed/test.json, /api/v1/feeds/trending-pairs, /api/v1/tools/base-analytics, /api/v1/tools/pdf-extractor, /api/v1/tools/render-screenshot, /api/v1/tools/extract-json, /api/v1/tools/smart-contract-verifier, /api/v1/tools/deploy-arc-contract, /api/v1/tools/arc-cctp-bridge, /api/v1/tools/real-estate-calculator, /api/v1/tools/address-normalizer, /api/v1/tools/weather-oracle, /api/v1/tools/forex-oracle, /api/v1/tools/shipping-rate-estimator, /api/v1/tools/github-health-analyzer, /api/v1/tools/property-comps-estimator

Actions (signed)

Every action is authorized with your private key; the server issues a one-shot challenge each time. Removal additionally re-checks the file on your domain, so a stolen key alone cannot remove a listing.
To run an action: open it below, choose your key file (or paste the key), click the action button, done. The key is read and used only in your browser and never leaves it; no command line needed.
Change contact email
The JSON key file from the claim page or a PKCS8 PEM works. The file is read locally in your browser and never uploaded.
Expert fallback: sign with openssl on the command line
Not needed for the normal flow above. Press "Get signing challenge" to see the exact message to sign (the nonce is part of it), sign it with printf '%s' '<message>' | openssl dgst -sha256 -sign provider-key.pem | base64 -w0, then send action, nonce and signature plus the action fields to this form's URL, for example with curl.
Update profile
The JSON key file from the claim page or a PKCS8 PEM works. The file is read locally in your browser and never uploaded.
Expert fallback: sign with openssl on the command line
Not needed for the normal flow above. Press "Get signing challenge" to see the exact message to sign (the nonce is part of it), sign it with printf '%s' '<message>' | openssl dgst -sha256 -sign provider-key.pem | base64 -w0, then send action, nonce and signature plus the action fields to this form's URL, for example with curl.
Provider alerts (email on failures)
Per endpoint. Checked endpoints mail you when they start failing their probes. Delisted endpoints start unchecked: they stay quiet by default, checking one opts it back in.
The JSON key file from the claim page or a PKCS8 PEM works. The file is read locally in your browser and never uploaded.
Expert fallback: sign with openssl on the command line
Not needed for the normal flow above. Press "Get signing challenge" to see the exact message to sign (the nonce is part of it), sign it with printf '%s' '<message>' | openssl dgst -sha256 -sign provider-key.pem | base64 -w0, then send action, nonce and signature plus the action fields to this form's URL, for example with curl.
Remove this host from the catalog
This removes every endpoint of api.warppay402.com from the public catalog (pages return 410), deletes the stored contact data, and blocklists the host: automated discovery will never add it again. Probe/settlement history stays internally as anonymous time series. As a fallback without your key, put x402-trust-remove into the verification file instead.
The JSON key file from the claim page or a PKCS8 PEM works. The file is read locally in your browser and never uploaded.
Expert fallback: sign with openssl on the command line
Not needed for the normal flow above. Press "Get signing challenge" to see the exact message to sign (the nonce is part of it), sign it with printf '%s' '<message>' | openssl dgst -sha256 -sign provider-key.pem | base64 -w0, then send action, nonce and signature plus the action fields to this form's URL, for example with curl.

Lost your key or need to change everything?

A full rotation replaces the provider key, the contact address and the profile of this claim in one go; the one-shot rotation link goes to the contact address on file for this claim.