x402basequality 0.30

Pay-per-call medical records endpoint on Base via x402, settling in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402 endpoint at lowpaymentfee.com serves medical record data behind a micropayment wall. The specific resource `/api/v1/medical/records/64` returns JSON content upon payment of 20,000 base-unit USDC (i.e., $0.02) on the Base network. Payment is handled via the x402 protocol: callers receive a 402 challenge with payment details and must include an X-PAYMENT header to access the resource.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs across categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. Settlement occurs on-chain via USDC (contract 0x8335…2913) on Base.

Important caveats: the endpoint's actual response schema is undocumented — there is no OpenAPI spec, no example responses, and no description of what fields a "medical record" contains. The category (medical records) suggests potentially regulated health data, but no compliance information (e.g., HIPAA) is provided. Callers should exercise caution and verify the nature and legitimacy of the data before relying on it.

Capabilities

x402-paymentusdc-basepay-per-callmedical-recordsjson-responseno-api-key

Use cases

  • Retrieving medical record data for record ID 64 via a single micropayment
  • Integrating pay-per-call health data into agent workflows without API key management
  • Demonstrating x402 protocol payment flows with a real endpoint

Fit

Best for

  • Developers experimenting with x402 micropayment protocol
  • Agents needing on-demand data access without subscription commitments
  • Projects requiring Base-network USDC settlement for API calls

Not for

  • Production healthcare applications requiring HIPAA-compliant data handling
  • Use cases needing documented response schemas or SLAs
  • Bulk retrieval of large medical datasets (pay-per-call at $0.02 each)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/64
# Returns 402 with x402 challenge. Include X-PAYMENT header with signed USDC payment on Base to access.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no response schema, no example responses, and no documentation about what the medical records endpoint actually returns. The regulated nature of medical data with zero compliance documentation further lowers confidence.

Warnings

  • No OpenAPI or response schema available — actual response content is unknown
  • Endpoint claims to serve 'medical records' but provides no compliance or regulatory information (e.g., HIPAA)
  • No documentation beyond the landing page listing; /api, /pricing, and /README pages are empty (wallet-connect only)
  • The legitimacy and nature of the 'medical record' data cannot be verified from available materials

Citations

Provenance

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

Agent access