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 a pay-per-call x402 protocol. The specific resource `/api/v1/hipaa/records/36` is described generically as "Premium API Access" by the provider. 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 x402 payment header.

The provider (lowpaymentfee.com) hosts a broad catalog of x402-gated endpoints spanning data analytics, AI/ML inference, finance, and utility services, all priced uniformly at $0.02 per request. However, the specific HIPAA records endpoint is not listed on the provider's public landing page, and no documentation, schema details, or example payloads are available for it. The crawled docs, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content.

Because this endpoint deals with HIPAA-labeled health records, callers should exercise caution regarding regulatory compliance (HIPAA, PHI handling). There is no documentation explaining what data is returned, what input is expected in the POST body, or whether the endpoint actually handles protected health information. The endpoint is live (returns a valid 402 challenge), but the lack of documentation makes it difficult to use without further investigation.

Capabilities

x402-paymenthipaa-recordspay-per-requestbase-networkusdc-settlementjson-responsepost-method

Use cases

  • Retrieving HIPAA-related health record data on a per-request basis
  • Integrating health record lookups into agent workflows with crypto micropayments
  • Accessing structured medical data without API key provisioning

Fit

Best for

  • Developers needing on-demand health record access with no subscription
  • Agent-based workflows requiring pay-per-call medical data
  • Prototyping healthcare integrations with low commitment

Not for

  • Production HIPAA-compliant systems requiring documented BAA agreements and audit trails
  • Use cases needing bulk or batch health record retrieval at scale
  • Anyone requiring clear regulatory compliance documentation before accessing PHI

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/36 \
  -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 schemas, no examples, and no explanation of what HIPAA records data is actually returned. The endpoint isn't even listed on the provider's own landing page. The HIPAA label raises significant regulatory concerns with no supporting compliance information.

Warnings

  • HIPAA-labeled endpoint with no documentation on compliance, BAA, or PHI handling — use with extreme caution
  • No request or response schema available; POST body format is unknown
  • Endpoint not listed on the provider's public API catalog
  • All documentation pages (docs, pricing, README) returned only 'Connect wallet' with no content
  • Regulatory risk: accessing or transmitting protected health information without proper compliance documentation

Citations

Provenance

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

Agent access