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/25` 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 with 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 priced at $0.02 per call. This particular endpoint falls under a healthcare/HIPAA category. However, the crawled documentation pages (docs, pricing, README) returned only a "Connect wallet" stub, so there is no detailed schema, field-level documentation, or example response available for this endpoint.

Because the endpoint path references "HIPAA records," it likely returns structured health-related data. The x402 challenge confirms the endpoint is live and accepting payment via the exact scheme on Base using USDC (contract 0x8335…2913). The payment address is 0x1A2B…85F3 with a max timeout of 300 seconds. Without further documentation, the exact request body format and response schema remain unknown.

Capabilities

x402-paymenthipaa-recordsper-request-billingusdc-baseno-api-keyhttp-post

Use cases

  • Retrieving structured HIPAA health record data on a per-request basis
  • Integrating health records into agent workflows without managing API keys
  • Paying for healthcare data access with USDC on Base L2

Fit

Best for

  • Agents needing on-demand access to health record data
  • Developers who want keyless, pay-per-call healthcare APIs
  • Web3-native applications consuming health data

Not for

  • Bulk or batch retrieval of large health datasets (no documented batch endpoint)
  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • Applications requiring non-crypto payment methods

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge confirms the endpoint is live and priced at $0.02 USDC on Base, but there is no OpenAPI schema, no request/response examples, and all documentation pages returned only a wallet-connect stub. The HIPAA label raises regulatory concerns with zero supporting documentation.

Warnings

  • Endpoint references HIPAA health records — a regulated data category — but no compliance documentation, privacy policy, or data handling details are available.
  • No request body schema or response schema documented; callers must guess the payload format.
  • All documentation pages (/docs, /pricing, /README, /api) returned only 'Connect wallet' with no usable content.
  • The specific record ID '25' in the path is opaque; it is unclear what data is returned or whether this is real PHI.

Citations

Provenance

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

Agent access