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/30` is described generically 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 lowpaymentfee.com hosts a broad catalog of x402-gated APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all uniformly priced at $0.02 per request. No API keys or rate limits are advertised; access is granted immediately upon valid x402 payment. However, this particular endpoint sits under a `/hipaa/records/` path, which implies it serves health-related data. No documentation, schema details, or example responses are available for this specific endpoint — the docs, pricing, and README pages all resolve to a minimal "Connect wallet" prompt.

Because the endpoint deals with HIPAA-labeled records, users should exercise caution regarding regulatory compliance (HIPAA, PHI handling). There is no published documentation explaining what data is returned, what input the POST body expects, or how protected health information is safeguarded. The endpoint is live (returns a valid 402 challenge), but the lack of any substantive documentation or schema makes it difficult to evaluate fitness for production use.

Capabilities

x402-paymentusdc-basehipaa-recordsper-request-billingno-api-keypost-endpoint

Use cases

  • Retrieving HIPAA-related health records on a per-request payment basis
  • Agent-driven access to medical data without pre-registration or API keys
  • Programmatic health data retrieval settled in USDC on Base

Fit

Best for

  • Developers needing on-demand HIPAA record access without subscription commitments
  • AI agents that can settle x402 payments in USDC on Base
  • Prototyping health data integrations with minimal setup

Not for

  • Production healthcare applications requiring documented HIPAA compliance guarantees
  • Users who need detailed API documentation or response schemas before integration
  • Applications requiring non-crypto payment methods

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on request/response schemas, no OpenAPI spec, and the docs pages are empty stubs. The HIPAA label raises regulatory concerns with no compliance information provided.

Warnings

  • Endpoint labeled 'HIPAA records' but no documentation on data content, PHI handling, or compliance measures is available.
  • No request body schema or response schema documented — impossible to know what to send or what is returned.
  • Docs, pricing, README, and API pages all render only a 'Connect wallet' prompt with no substantive content.
  • Health data endpoints may be subject to HIPAA and other regulatory requirements — verify compliance independently.

Citations

Provenance

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

Agent access