x402basequality 0.30

Pay-per-call medical records endpoint on Base via x402, settled in USDC.

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 77) via the x402 payment protocol. It accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced uniformly at $0.02 per request. The specific resource at `/api/v1/medical/records/77` is labeled "Premium API Access" in the x402 challenge but is not described in the site's public API listing, so the exact data schema and fields returned are unknown.

The endpoint is live and returns a well-formed x402 challenge (HTTP 402) with version 1, a 300-second payment timeout, and the exact payment scheme targeting USDC on Base. Because this endpoint deals with medical records, callers should be aware of potential regulatory considerations (e.g., HIPAA in the US) — the platform provides no documentation on data provenance, compliance, or privacy safeguards.

Capabilities

x402-paymentusdc-settlementbase-networkmedical-recordspay-per-callno-api-keyjson-response

Use cases

  • Retrieving medical record data for record ID 77 via a single paid API call
  • Integrating pay-per-call medical data access into agent workflows
  • Demonstrating x402 micropayment protocol usage for health data

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents needing on-demand medical record access without API key management
  • Micropayment-based data retrieval without subscriptions

Not for

  • Production healthcare applications requiring HIPAA compliance guarantees
  • Bulk medical data retrieval or batch processing
  • Users who need detailed documentation or schema definitions before integration

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation on the request body schema, response format, or what medical data is actually returned. The endpoint is not listed on the provider's own landing page. The medical/health category raises regulatory concerns with zero compliance information provided.

Warnings

  • Endpoint deals with medical records but provides no documentation on data provenance, privacy, or regulatory compliance (e.g., HIPAA).
  • This specific endpoint (/api/v1/medical/records/77) is not listed on the provider's public API catalog — its contents and schema are unknown.
  • No request body schema or response schema is documented anywhere.
  • No OpenAPI spec, README, or detailed docs are available (crawled pages returned only 'Connect wallet').

Citations

Provenance

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

Agent access