x402basequality 0.30

Pay-per-call email data endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at `/api/v1/emails/65` is part of the lowpaymentfee.com platform, which offers a collection of pay-per-request APIs spanning data & analytics, AI/ML, finance, infrastructure, and more. Each call is settled on the Base network using USDC (contract 0x8335…2913) with no API keys, no rate limits, and no subscriptions required — just an x402 payment header per request.

The specific endpoint probed (`/api/v1/emails/65`) is labeled "Premium API Access" and accepts POST requests. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The response MIME type is `application/json`. However, the crawled documentation is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further detail. There is no OpenAPI spec, no request/response schema, and no description of what the `/emails/65` endpoint actually returns or what input it expects.

Because the endpoint path suggests email-related data (possibly an email record lookup or email validation service) but no documentation confirms this, the actual functionality remains unclear. The platform's landing page lists many API categories but does not include an explicit emails category, making this endpoint's purpose ambiguous. Agents should treat this as a live, payable endpoint but should be aware that the lack of documentation means the request format and response structure are unknown.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyjson-responseemail-data

Use cases

  • Retrieving email-related data on a per-request payment basis
  • Agent-driven API consumption without pre-registration or API keys
  • Micropayment-gated data access settled on Base L2

Fit

Best for

  • Agents needing keyless, pay-as-you-go API access
  • Developers experimenting with x402 payment protocol
  • Use cases requiring low-friction, no-subscription data endpoints

Not for

  • Production workloads requiring well-documented request/response schemas
  • High-volume batch processing where per-call pricing is inefficient
  • Users who need detailed API documentation before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/emails/65 \
  -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 with clear pricing, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the actual purpose of the /emails/65 endpoint is undocumented. Functionality must be guessed from the URL path alone.

Warnings

  • No OpenAPI or schema documentation available — request body format and response structure are completely unknown.
  • The /emails/65 endpoint is not listed among the platform's advertised API categories, making its purpose ambiguous.
  • Docs, pricing, API, and README pages all render only 'Connect wallet' with no usable content.
  • Endpoint functionality is inferred solely from the URL path; actual behavior is unverified.

Citations

Provenance

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

Agent access