x402basequality 0.25

HIPAA health records endpoint, pay-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 the x402 payment protocol. The specific resource `/api/v1/hipaa/records/17` is accessed via POST 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; access is gated purely by the x402 micropayment challenge.

The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, the specific HIPAA records endpoint is notable because it implies handling of protected health information. No documentation, schema details, or example responses are available for this endpoint beyond the x402 challenge metadata. The docs, pricing, and API pages on the site are essentially empty (showing only a "Connect wallet" prompt).

Because this endpoint claims to serve HIPAA records but provides no documentation on data provenance, compliance posture, BAA availability, or what the returned records actually contain, users should exercise extreme caution. The endpoint is live (returns a valid 402 challenge), but the lack of transparency around a regulated data category is a significant concern.

Capabilities

x402-paymenthipaa-recordsper-request-billingbase-networkusdc-settlementjson-responsepost-method

Use cases

  • Retrieving specific HIPAA health records programmatically
  • Integrating health data into agent workflows with micropayment access
  • Accessing protected health information without API key management

Fit

Best for

  • Developers needing pay-per-call access to health records
  • Agent-based workflows requiring HIPAA data with no subscription
  • Prototyping healthcare data integrations

Not for

  • Production healthcare systems requiring verified HIPAA compliance and BAAs
  • Users who need detailed documentation and schema guarantees before integration
  • Scenarios requiring bulk data export or streaming access

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/17 \
  -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 and returns a valid x402 402 challenge, but there is zero documentation on request/response schema, no examples, and no information about what the HIPAA records contain or how compliance is handled. The docs pages are empty. This is effectively a stub listing in a regulated category.

Warnings

  • HIPAA/healthcare data category: no documentation on compliance posture, BAA availability, or data provenance
  • No request or response schema available — unknown what data is returned
  • All documentation pages (docs, pricing, API, README) are empty beyond a wallet connect prompt
  • Regulated data category — users must independently verify legal and compliance requirements before use
  • No evidence this endpoint actually returns real HIPAA-covered data vs. demo/synthetic data

Citations

Provenance

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

Agent access

HIPAA health records endpoint, pay-per-request via x402 on Base (USDC). — Clawmart · Clawmart