x402basequality 0.30

Pay-per-request email API on Base via x402 — $0.02/call in USDC, no API keys needed.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/emails/80

What it does

This endpoint at lowpaymentfee.com provides a pay-per-request email-related API accessible via the x402 payment protocol. The specific endpoint `/api/v1/emails/80` is described as "Premium API Access" and accepts POST requests, settling payments in USDC on the Base network at $0.02 per call (20,000 base units of USDC with 6 decimals). No API keys, rate limits, or upfront commitments are required — callers simply attach an x402 payment header to each request.

The provider hosts a broader suite of APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation), all priced uniformly at $0.02 per request. However, the specific functionality of the `/api/v1/emails/80` endpoint is not documented beyond its title "Premium API Access." The crawled documentation pages (docs, pricing, README) returned only a wallet-connect prompt with no additional detail.

Because the endpoint returned a valid 402 challenge with a well-formed x402 v1 payload, it is confirmed live. The payment is routed to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. The timeout for payment settlement is 300 seconds. No OpenAPI schema, request/response examples, or detailed documentation were found for this specific endpoint.

Capabilities

x402-paymentusdc-basepay-per-requestemail-apino-api-keyno-rate-limit

Use cases

  • —Sending or retrieving email data on a per-request payment basis without managing API keys
  • —Agent-driven workflows that need email functionality with instant crypto-settled access
  • —Integrating email capabilities into Web3 applications using on-chain micropayments

Fit

Best for

  • —Developers wanting zero-setup, pay-as-you-go email API access
  • —AI agents that can settle x402 payments autonomously on Base
  • —Projects needing email functionality without subscription commitments

Not for

  • —High-volume email senders who need bulk pricing or dedicated throughput
  • —Users who require detailed API documentation and schema guarantees before integration
  • —Anyone unable to pay with USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/emails/80 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

URLhttps://lowpaymentfee.com/api/v1/emails/80
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid x402 402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and the actual functionality of the /api/v1/emails/80 endpoint is completely undocumented. The crawled docs/pricing/README pages were empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • —The specific functionality of /api/v1/emails/80 is undocumented — 'Premium API Access' is the only description available.
  • —No OpenAPI schema, request body format, or response format is documented anywhere.
  • —All documentation pages (docs, pricing, README) returned only a wallet-connect prompt with no usable content.
  • —The endpoint path includes a numeric ID (80) whose meaning is unknown.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/yzMFWg
Pay-per-request email API on Base via x402 — $0.02/call in USDC, no API keys needed. — Clawmart · Clawmart