x402basequality 0.25

HIPAA health records endpoint payable 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/47` is accessed via POST and returns JSON. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys, rate limits, or upfront commitments are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The provider, lowpaymentfee.com, hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced uniformly at $0.02 per request. This particular endpoint falls under a "HIPAA records" path, but the crawled documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further detail. There is no OpenAPI spec, no request/response schema documentation, and no description of what fields the HIPAA records endpoint accepts or returns.

Because the endpoint path references HIPAA (Health Insurance Portability and Accountability Act) data, callers should exercise caution: there is no visible evidence of HIPAA compliance certifications, BAA (Business Associate Agreement) availability, or any privacy/security documentation on the site. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it impossible to verify what data is actually served or what input is expected.

Capabilities

x402-paymentper-request-billingusdc-base-networkhipaa-recordsjson-responsepost-method

Use cases

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

Fit

Best for

  • Developers needing on-demand HIPAA record access without subscription commitments
  • AI agents that can settle x402 payments on Base
  • Prototyping health data integrations with low per-call costs

Not for

  • Production healthcare systems requiring verified HIPAA compliance and BAAs
  • Use cases needing bulk data export or streaming access
  • Organizations that cannot transact in USDC on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base), but there is zero documentation on request format, response schema, or what data is actually returned. The HIPAA label raises serious compliance concerns with no supporting evidence. Docs pages are empty.

Warnings

  • No OpenAPI spec or request/response schema available — input and output formats are unknown
  • Endpoint claims to serve HIPAA records but no HIPAA compliance documentation, certifications, or BAA information is visible on the site
  • All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
  • Regulated health data category — callers should verify legal and compliance requirements independently
  • The specific record ID '47' in the path is hardcoded; it is unclear how to query other records

Citations

Provenance

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

Agent access

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