x402basequality 0.30

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/5` is accessed via HTTP POST and costs $0.02 per request, settled in USDC on the Base network. No API keys or rate limits are required; callers simply attach an x402 payment header to each request.

The broader lowpaymentfee.com platform hosts a variety of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all at a uniform $0.02/request price point. However, this specific listing covers the HIPAA records endpoint. The x402 challenge confirms the endpoint is live, accepting payments to address `0x1A2B...85F3` using USDC (`0x8335...2913`) on Base.

Important caveats: the crawled documentation pages (docs, pricing, README) all returned only a "Connect wallet" stub with no substantive content. There is no OpenAPI schema, no request/response examples, and no documentation describing what data the HIPAA records endpoint actually returns, what input it expects in the POST body, or what "records/5" refers to. The endpoint's name references HIPAA (health data privacy regulation), which implies it may handle protected health information — a regulated category that warrants caution.

Capabilities

x402-paymentper-request-billingusdc-settlementbase-networkhipaa-recordshealth-datano-api-keypost-endpoint

Use cases

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

Fit

Best for

  • Developers needing on-demand HIPAA record lookups without subscription commitments
  • AI agents that can settle x402 payments in USDC on Base
  • Prototyping health-data integrations with minimal setup

Not for

  • Production healthcare systems requiring full HIPAA compliance documentation and BAAs
  • Users who need detailed API documentation or guaranteed SLAs
  • Non-crypto users who cannot settle payments on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and confirms pricing and payment details, but there is zero documentation on request format, response schema, or what the endpoint actually returns. All doc pages are stubs. The HIPAA label raises regulatory concerns with no supporting compliance information.

Warnings

  • No API documentation available — all doc pages return only 'Connect wallet' stubs
  • No request or response schema provided; unknown what POST body is expected
  • Endpoint references HIPAA (regulated health data) but no compliance documentation, BAA, or privacy policy is available
  • The specific meaning of 'records/5' is undocumented — unclear if this is a fixed resource or parameterized path
  • No OpenAPI spec or examples exist to verify actual functionality

Citations

Provenance

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

Agent access