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/100` accepts POST requests and charges $0.02 per call, 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 priced uniformly at $0.02 per request. However, the specific HIPAA records endpoint is notable because it implies access to health-related data, which falls under regulated categories. No documentation, schema details, or example responses are available for this endpoint beyond the x402 challenge and the landing page listing. The docs, pricing, and API pages all resolve to a minimal "Connect wallet" prompt with no further technical detail.

Because the endpoint's actual response payload, input schema, and data source are undocumented, callers should exercise caution. The HIPAA label suggests health data subject to regulatory requirements, but no compliance certifications or data provenance information is provided.

Capabilities

x402-paymenthipaa-recordsper-request-billingusdc-basepost-endpointno-api-key

Use cases

  • Retrieving health record data on a per-request payment basis
  • Integrating HIPAA-labeled data into agent workflows without API key management
  • Programmatic access to health records settled in USDC on Base

Fit

Best for

  • Agents needing on-demand health record lookups with crypto micropayments
  • Developers exploring x402 pay-per-call patterns for regulated data
  • Workflows requiring keyless, instant API access to health data

Not for

  • Production healthcare applications requiring verified HIPAA compliance documentation
  • Use cases needing detailed API documentation, schemas, or SLAs
  • Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid 402 x402 challenge), but there is zero documentation on request/response schemas, no examples, and no information about what data is actually returned. The HIPAA label raises regulatory concerns with no compliance evidence provided. Docs pages are empty stubs.

Warnings

  • HIPAA-labeled endpoint with no documented compliance certifications or data provenance
  • No request or response schema documentation available
  • All documentation pages (docs, pricing, API, README) resolve to a minimal 'Connect wallet' stub with no technical content
  • Regulated health data category — verify legal and compliance requirements before use

Citations

Provenance

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

Agent access