Retrieve email attachments via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to email attachments (specifically email ID 26) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) 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 include an X-PAYMENT header with a valid x402 payment proof.
The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and utility services — all priced at $0.02 per request on the Base network. However, this specific endpoint (`/api/v1/emails/26/attachments`) is not listed on the site's public API catalog, and no documentation describes its request body schema, expected input parameters, or response format. The endpoint is live and returns a valid x402 challenge, but the actual functionality and data returned remain unclear.
Because the endpoint path references a specific email ID (26) and "attachments," it likely returns attachment metadata or file content for a particular stored email. Without documentation or example responses, the exact behavior is speculative. The platform's landing page confirms the $0.02 pricing model and Base network settlement, but offers no further detail on this particular route.
Capabilities
Use cases
- —Retrieving attachments from a stored email via programmatic API call
- —Agent-driven email attachment fetching with automatic micropayment
- —Accessing email data without traditional API key provisioning
Fit
Best for
- —Agents that need to fetch email attachments with zero-setup authentication
- —Developers experimenting with x402 pay-per-call patterns on Base
- —Workflows requiring on-demand email attachment retrieval without subscriptions
Not for
- —Bulk email processing or mailbox management — this targets a single email ID
- —Users needing documented, well-specified API contracts with full schema coverage
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/emails/26/attachments \
-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, no examples, and the endpoint is not even listed in the provider's own public API catalog. The purpose of fetching 'email 26 attachments' is opaque. This is effectively a stub listing.
Warnings
- —Endpoint /api/v1/emails/26/attachments is not listed in the provider's public API catalog — its purpose and data are unclear.
- —No request body schema or response schema is documented anywhere.
- —The endpoint references a hardcoded email ID (26); it is unclear whether other email IDs are supported or what data is returned.
- —Documentation pages (/docs, /api, /pricing, /README) all returned only 'Connect wallet' with no substantive content.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 in USDC on Base network.https://lowpaymentfee.com/api/v1/emails/26/attachments
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and Base network settlement.https://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimals, making 20000 base units equal to $0.02.https://lowpaymentfee.com