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 specific medical record (record ID 56) behind an x402 paywall. 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 hosts dozens of pay-per-call APIs across categories including data analytics, AI/ML inference, finance, and infrastructure utilities, all priced at $0.02 per request. However, the specific content and schema of the medical records response for this endpoint are not documented. The endpoint returned a valid 402 challenge during probing, confirming it is live.

Important caveat: this endpoint appears to serve medical record data, which falls under regulated health data categories in many jurisdictions. No documentation was found describing the data source, compliance posture (e.g., HIPAA), or what fields are returned. Callers should exercise caution and verify regulatory compliance before integrating.

Capabilities

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

Use cases

  • Retrieving a specific medical record (ID 56) programmatically
  • Agent-driven health data retrieval with micropayment settlement
  • Integrating medical record lookups into automated workflows

Fit

Best for

  • Agents needing on-demand medical record access without API key management
  • Developers experimenting with x402 pay-per-call patterns
  • Workflows requiring single-record lookups with instant crypto settlement

Not for

  • Bulk medical record retrieval or batch processing (single record endpoint)
  • Production healthcare applications requiring HIPAA-compliant audit trails (compliance status unknown)
  • Users without Base network USDC for payment

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/medical/records/56 \
  -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 (valid 402 challenge captured), but there is no documentation on request body schema, response schema, or what medical record data is actually returned. The endpoint serves regulated health data with no visible compliance information. No OpenAPI spec, no examples, and crawled pages beyond the landing page returned only 'Connect wallet' stubs.

Warnings

  • Regulated category: endpoint serves medical record data with no documented HIPAA or health data compliance posture
  • No request or response schema documented — callers cannot know what fields to send or expect
  • Only a single hardcoded record ID (56) is exposed at this URL; unclear if other record IDs are available
  • No privacy policy, terms of service, or data provenance information found
  • Crawled documentation pages (/api, /pricing, /README) returned no useful content

Citations

Provenance

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

Agent access