x402basequality 0.25

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/70` is described by the provider as "Premium API Access" and accepts POST requests. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units of USDC with 6 decimals).

The provider operates a broader platform offering dozens of x402-gated API endpoints across categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all uniformly priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, documentation beyond the landing page is essentially empty (all doc/pricing/README pages just show a "Connect wallet" prompt), so the actual behavior, request schema, and response format of this specific HIPAA records endpoint are unknown.

Because this endpoint claims to serve HIPAA health records, users should exercise caution. There is no visible documentation explaining what data is returned, how PHI (Protected Health Information) is handled, or whether the provider is HIPAA-compliant. The endpoint is live and returns a valid x402 challenge, but the lack of documentation and the sensitive nature of health data are significant concerns.

Capabilities

x402-paymentusdc-basehipaa-recordsper-request-billingpost-endpointno-api-key

Use cases

  • Retrieving specific HIPAA health records programmatically
  • Integrating health data into agent workflows with per-call payment
  • Accessing medical record data without subscription or API key management

Fit

Best for

  • Agents needing on-demand health record lookups with crypto payment
  • Developers exploring x402-gated health data endpoints
  • Low-volume, pay-as-you-go access to health records

Not for

  • Production healthcare applications requiring verified HIPAA compliance documentation
  • High-volume bulk medical data retrieval (no documented rate limits but no SLA either)
  • Users who need detailed API documentation or response schema before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/70 \
  -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 challenge, but there is zero documentation on request/response schemas, no OpenAPI spec, and no explanation of what data is actually returned. The HIPAA/health claim is unverified and raises regulatory concerns. All non-landing pages are empty.

Warnings

  • No API documentation available — all doc pages return only 'Connect wallet' with no content
  • Endpoint claims to serve HIPAA health records but provides no evidence of HIPAA compliance, BAA availability, or PHI handling practices
  • Request and response schemas are completely unknown — no OpenAPI spec or examples provided
  • The provider hosts many diverse endpoints (AI, finance, geocoding, HIPAA) all at $0.02, which raises questions about the authenticity and depth of the data returned
  • Regulated health data category — verify compliance before use in any production or clinical context

Citations

Provenance

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

Agent access

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