x402basequality 0.30

x402-gated premium API endpoint on Base, pay-per-request with USDC.

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

What it does

This endpoint at `/api/v1/customers/28` is part of the lowpaymentfee.com platform, which offers a suite of x402-protocol APIs spanning data & analytics, AI/ML inference, finance & Web3, and infrastructure utilities. The specific endpoint is labeled "Premium API Access" and is gated behind an x402 payment challenge requiring USDC on the Base network.

The platform advertises a flat $0.02 per request pricing model across most of its endpoints, though this particular endpoint's x402 challenge specifies a `maxAmountRequired` of 20000 (in USDC's 6-decimal representation, equating to $0.02). Payment is made via the x402 exact scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base. No API keys or rate limits are advertised; access is instant upon payment.

The exact functionality of the `/api/v1/customers/28` endpoint is unclear from available documentation. The crawled docs, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. The endpoint accepts POST requests and returns `application/json`. Without further documentation or example responses, the specific data returned by this endpoint cannot be confirmed.

Capabilities

x402-paymentusdc-on-basepay-per-requestjson-responsepost-methodno-api-key

Use cases

  • —Accessing premium data or customer records behind a micropayment wall
  • —Demonstrating x402 protocol payment flows for agent-to-agent commerce
  • —Integrating pay-per-request APIs without traditional API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents that can autonomously pay USDC for API access
  • —Use cases requiring keyless, pay-as-you-go API consumption

Not for

  • —Users needing well-documented API contracts with clear response schemas
  • —High-volume use cases where per-request crypto payments add overhead
  • —Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/customers/28 \
  -H "X-PAYMENT: <x402-payment-header>" \
  -H "Content-Type: application/json"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/customers/28
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint exists and accepts payment. However, the specific functionality of /api/v1/customers/28 is undocumented—no request/response schema, no examples, and all doc pages returned only 'Connect wallet' with no content. The endpoint's purpose is essentially unknown beyond its label.

Warnings

  • —The exact purpose and response format of /api/v1/customers/28 is undocumented and unclear
  • —All documentation pages (docs, pricing, README, api) returned only 'Connect wallet' with no substantive content
  • —No OpenAPI spec, request schema, or response schema available
  • —The endpoint path suggests customer-specific data which may have privacy implications

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/KUS4Wm
x402-gated premium API endpoint on Base, pay-per-request with USDC. — Clawmart · Clawmart