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/81

What it does

This endpoint at lowpaymentfee.com provides "Premium API Access" via the x402 payment protocol. The specific resource `/api/v1/accounts/81` is one of many endpoints offered by the platform, which spans data & analytics, AI & machine learning, finance & Web3, and infrastructure utility categories. All endpoints are priced at $0.02 per request, settled in USDC on the Base network with no API keys, no rate limits, and no commitments required.

The x402 challenge confirms the endpoint is live, accepting POST requests and requiring an exact payment of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) per call. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a maximum timeout of 300 seconds. The response MIME type is application/json.

However, the specific functionality behind `/api/v1/accounts/81` is unclear. The provider's landing page lists various API categories (metrics, reports, sentiment analysis, summarization, price feeds, geocoding, etc.) but does not document this particular accounts endpoint. No OpenAPI spec, request/response schemas, or detailed documentation were found in the crawl. The docs, pricing, API, and README pages all returned only a "Connect wallet" prompt with no substantive content. As a result, the actual data returned by this endpoint and the expected request body format remain unknown.

Capabilities

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

Use cases

  • —Accessing premium data or account information with per-request USDC micropayments
  • —Integrating pay-as-you-go API calls into agent workflows without API key management
  • —Testing x402 payment protocol integrations on Base network

Fit

Best for

  • —Developers experimenting with x402 payment-gated APIs
  • —Agents that need keyless, pay-per-call API access on Base
  • —Low-volume consumers who prefer no subscription commitments

Not for

  • —Users needing well-documented API contracts with clear request/response schemas
  • —High-volume use cases where per-request crypto payments add overhead
  • —Anyone requiring non-crypto payment methods

Quick start

# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# Using curl as a conceptual example (actual payment header must be constructed per x402 spec):
curl -X POST https://lowpaymentfee.com/api/v1/accounts/81 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but the specific endpoint's purpose, request format, and response schema are entirely undocumented. No OpenAPI spec exists, and all documentation pages returned only a wallet-connect prompt with no content.

Warnings

  • —The specific functionality of /api/v1/accounts/81 is not documented anywhere on the site
  • —No OpenAPI spec, request schema, or response schema available
  • —All documentation pages (docs, pricing, API, README) returned only 'Connect wallet' with no substantive content
  • —The 'accounts/81' path suggests a resource-specific endpoint but its purpose is unknown

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 00:46:35Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

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