Pay-per-call email data endpoint on Base via x402, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides premium API access to an email-related resource (ID 54) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced uniformly at $0.02 per request. However, the specific endpoint probed (/api/v1/emails/54) is not listed on the site's public catalog, so its exact functionality is unclear. The path suggests it returns data about or related to a specific email record (ID 54), but no schema, documentation, or example responses are available to confirm what fields are returned.
The endpoint is live and responds with a well-formed x402 challenge (HTTP 402). The payment timeout is 300 seconds. The platform advertises no minimums, no commitments, and instant access. Documentation pages (/docs, /pricing, /README) all returned only a "Connect wallet" prompt with no substantive content during the crawl.
Capabilities
Use cases
- —Retrieving email-related data for a specific record via a single paid API call
- —Integrating pay-per-use email data into agent workflows without managing API keys
- —Programmatic access to email metadata settled on-chain via USDC on Base
Fit
Best for
- —Agents or bots that need on-demand email data without subscription overhead
- —Developers experimenting with x402 pay-per-call protocols
- —Workflows requiring keyless, permissionless API access
Not for
- —Bulk email sending or transactional email delivery
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —High-volume use cases where per-call pricing may add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/emails/54 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the specific /emails/54 path is not listed on the provider's own catalog. It is impossible to determine what this endpoint actually returns without paying for a call. Docs pages are empty.
Warnings
- —The /api/v1/emails/54 endpoint is not listed in the provider's public API catalog — its purpose and output are unknown.
- —All documentation pages (/docs, /pricing, /README) returned no useful content during crawl.
- —No request body schema or response schema is available; callers cannot know what to send or what to expect back.
- —The endpoint path suggests a single fixed resource (ID 54) rather than a parameterized query, which limits utility.
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/emails/54
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/emails/54
- —The platform advertises $0.02/request, no API keys, no rate limits, instant access, Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/emails/54