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 71) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled in USDC on the Base network at $0.02 per call (maxAmountRequired of 20,000 base units with 6 decimals = $0.02), with no API keys, rate limits, or subscriptions required.
The provider lowpaymentfee.com hosts a broader suite of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto data feeds, and infrastructure utilities — all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/emails/71/attachments` endpoint. The endpoint's purpose and response schema are not documented beyond the generic "Premium API Access" label, so the exact structure of the returned attachment data is unknown.
The endpoint is live: it returns a well-formed x402 version 1 challenge with an "exact" payment scheme targeting USDC (contract 0x8335…2913) on Base. The payment recipient is 0x1A2B…85F3 with a 300-second timeout. No OpenAPI spec, detailed docs, or example responses were found in the crawl — the docs, pricing, and API pages all render only a wallet-connect prompt with no additional technical content.
Capabilities
Use cases
- —Programmatically retrieving email attachments via a pay-per-request model
- —Agent-driven workflows that need to fetch specific email attachment data without API key provisioning
- —Demonstrating x402 micropayment integration on the Base network
Fit
Best for
- —Agents or scripts that need one-off email attachment retrieval without signup
- —Developers experimenting with x402 payment protocol on Base
- —Workflows requiring keyless, pay-as-you-go API access
Not for
- —Bulk email processing or high-volume attachment downloads (no documented batch support)
- —Users who need detailed documentation or guaranteed SLAs
- —Accessing arbitrary email IDs (this endpoint is hardcoded to email 71)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/emails/71/attachments \
-H "X-PAYMENT: <x402_payment_token>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI spec, no documented request/response schema, no example payloads, and the docs pages are empty beyond a wallet-connect prompt. The endpoint path suggests a single hardcoded email ID (71), and the purpose of the attachment data is unclear. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown.
- —Endpoint is scoped to a single email ID (71); unclear if other email IDs are supported.
- —Docs, pricing, and API pages render only a wallet-connect prompt with no technical content.
- —The exact nature of the 'email attachments' data is undocumented — could be demo/test data.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/emails/71/attachments
- —All APIs on lowpaymentfee.com are priced at $0.02 per request with no API keys, rate limits, or minimumshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/emails/71/attachments