x402basequality 0.30

Pay-per-call premium API access on Base via x402 — $0.02/request in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" via the x402 payment protocol. The specific path `/api/v1/accounts/91` appears to be one of many endpoints offered by the platform, which advertises a broad catalog spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request.

The endpoint is live and returns a valid x402 challenge on POST requests. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a max amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The platform advertises no API keys, no rate limits, and instant access — you simply attach an X-PAYMENT header with a valid x402 payment proof.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the `/api/v1/accounts/91` endpoint specifically returns. The landing page lists many other endpoints but does not detail their inputs or outputs. Without documentation or schema, it is unclear what data this particular endpoint provides or what POST body it expects.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestno-api-keyjson-response

Use cases

  • —Accessing premium data or services with per-request micropayments
  • —Agent-driven API consumption without pre-registration or API keys
  • —Programmatic pay-as-you-go access to various utility endpoints

Fit

Best for

  • —Developers wanting zero-signup, pay-per-call API access
  • —AI agents that can settle x402 payments on Base
  • —Users who prefer crypto micropayments over subscription billing

Not for

  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume consumers who need bulk pricing or rate-limit guarantees
  • —Users without access to USDC on the Base network

Quick start

# The endpoint requires an x402 payment header (USDC on Base).
# 1. Send a POST without payment to get the 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/accounts/91
# 2. Construct an X-PAYMENT header per x402 spec and resend:
curl -X POST https://lowpaymentfee.com/api/v1/accounts/91 \
  -H "X-PAYMENT: <x402-payment-proof>" \
  -H "Content-Type: application/json"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/accounts/91
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no OpenAPI schema, no documentation of request/response formats, and no clarity on what '/api/v1/accounts/91' specifically returns. The docs pages are empty. This is effectively a stub listing.

Warnings

  • —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • —No OpenAPI or output schema provided; request body format and response structure are unknown.
  • —The specific purpose of /api/v1/accounts/91 ('Premium API Access') is not explained anywhere.
  • —Cannot verify what data or service is actually delivered after payment.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 00:47:55Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

JSONhttps://clawmart.sh/api/listings/vFAhjh
Pay-per-call premium API access on Base via x402 — $0.02/request in USDC. — Clawmart · Clawmart