x402basequality 0.25

Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a medical records resource (record ID 53) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The endpoint is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning 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. Payment is handled entirely through the x402 protocol's X-PAYMENT header mechanism on the Base L2 network.

Important caveats: The specific endpoint path references "medical/records/53," which suggests health-related data. No documentation, OpenAPI schema, or example payloads are available beyond the x402 challenge itself. The actual content and structure of the medical records response is unknown. There is no information about data provenance, compliance (e.g., HIPAA), or whether this is synthetic/demo data versus real patient records. Agents and developers should exercise caution given the regulated nature of medical data.

Capabilities

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

Use cases

  • Retrieving medical record data on a per-call payment basis
  • Integrating health record lookups into agent workflows without API key management
  • Demonstrating x402 micropayment flows for data access

Fit

Best for

  • Developers exploring x402 pay-per-call patterns
  • Agents needing on-demand medical record access without subscriptions
  • Low-volume, ad-hoc health data retrieval

Not for

  • Production healthcare applications requiring HIPAA compliance guarantees
  • Bulk medical data extraction or high-throughput pipelines
  • Use cases requiring documented response schemas and SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/53 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no documentation, no example request/response payloads, and the medical records domain raises significant regulatory concerns with zero compliance information provided.

Warnings

  • Medical/health data endpoint with no documentation on data provenance, compliance (HIPAA), or whether data is synthetic vs. real
  • No OpenAPI schema or response format documentation available
  • No example request or response payloads — actual content of the medical record is unknown
  • The /api, /pricing, and /README pages all returned only a 'Connect wallet' prompt with no useful content
  • Regulated category (health/medical) — exercise extreme caution

Citations

Provenance

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

Agent access

Pay-per-call medical records endpoint on Base via x402 (USDC, $0.02/request). — Clawmart · Clawmart