x402basequality 0.25

HIPAA health records endpoint paid per-request via x402 on Base (USDC).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to HIPAA-related health records via a pay-per-call x402 protocol. The specific resource `/api/v1/hipaa/records/95` is described generically as "Premium API Access" and accepts POST requests. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units of USDC with 6 decimals).

The broader lowpaymentfee.com platform hosts a variety of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all uniformly priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access; callers pay by attaching an x402 payment header with each request. However, the HIPAA records endpoint is not listed on the site's public landing page, and no documentation, request/response schema, or example payloads are available for it. The docs, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content.

Because the endpoint deals with HIPAA records — a regulated healthcare data category — callers should exercise caution. There is no published documentation explaining what data is returned, what input is expected, or what compliance measures are in place. The endpoint is live (returns a valid 402 x402 challenge), but the lack of transparency around the data model and regulatory compliance is a significant concern.

Capabilities

x402-paymentusdc-settlementbase-networkhipaa-recordsper-request-billingpost-method

Use cases

  • Retrieving specific HIPAA health records on a per-request payment basis
  • Integrating health data into agent workflows without API key management
  • Programmatic access to medical record data settled via crypto micropayments

Fit

Best for

  • Agents needing on-demand access to health record data without subscription commitments
  • Developers experimenting with x402 pay-per-call patterns for healthcare data
  • Workflows requiring keyless, instant API access to HIPAA records

Not for

  • Production healthcare applications requiring verified HIPAA compliance documentation
  • High-volume bulk retrieval of medical records (no documented batch support)
  • Users who need detailed API documentation or response schema guarantees before calling

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response format, no OpenAPI schema, and the HIPAA records endpoint is not even listed on the provider's landing page. The docs and other pages are empty. The regulated healthcare category with no compliance information further lowers confidence.

Warnings

  • HIPAA/healthcare data category: no compliance documentation or BAA information is published
  • This specific endpoint (/api/v1/hipaa/records/95) is not listed on the provider's public API catalog
  • No request or response schema is available — callers cannot know what to send or what to expect
  • All documentation pages (docs, pricing, README) render only a 'Connect wallet' prompt with no content
  • Regulated health data: verify legal and compliance requirements before use in any production context

Citations

Provenance

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

Agent access