x402basequality 0.30

Retrieve email attachments via x402 micropayment on Base for $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to email attachments (specifically email ID 33) 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 upfront commitments 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 endpoint (/api/v1/emails/33/attachments) is not listed on the provider's landing page among the advertised API categories. Its purpose — retrieving attachments for a specific email — is unclear in context, and no documentation, request schema, or response schema is available beyond the x402 challenge itself.

The endpoint is live and returns a valid x402 challenge (HTTP 402) with x402Version 1, paying to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base. The timeout is 300 seconds. No OpenAPI spec, AI plugin manifest, or detailed documentation was found during crawl.

Capabilities

x402-paymentemail-attachmentsusdc-basemicropaymentpost-json

Use cases

  • Retrieving email attachments programmatically via a pay-per-call model
  • Agents accessing gated email content without API key registration
  • Automated workflows that need to fetch specific email attachments on demand

Fit

Best for

  • Agents needing keyless, pay-per-use access to email attachments
  • Workflows requiring instant access without signup or rate limits
  • x402-compatible clients on the Base network

Not for

  • Bulk email processing or high-volume attachment downloads (no documented batch support)
  • Users who need documentation or schema guarantees before integrating
  • Accessing emails other than ID 33 (endpoint is hardcoded to a single email)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/emails/33/attachments \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the endpoint is not listed among the provider's advertised APIs. The purpose of accessing 'email 33 attachments' is opaque with no context. Effectively a stub listing.

Warnings

  • This specific endpoint (/api/v1/emails/33/attachments) is not listed on the provider's landing page among advertised APIs — its purpose and legitimacy are unclear.
  • No request or response schema is available; the output format is unknown beyond mimeType application/json.
  • No documentation pages returned meaningful content (all showed only 'Connect wallet').
  • The endpoint is hardcoded to email ID 33; it is unclear whether other email IDs are supported or what data is returned.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 19:10:08Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access