x402basequality 0.25

HIPAA health records endpoint, pay-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/19` is described 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). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced uniformly at $0.02 per call. However, the specific HIPAA records endpoint is not listed on the provider's public landing page among the advertised API categories, and no documentation, request/response schema, or example payloads are available for this particular resource. The docs, pricing, and README pages all resolve to a minimal "Connect wallet" prompt with no further content.

Because this endpoint deals with HIPAA-labeled health records, consumers should exercise caution regarding data provenance, compliance obligations, and whether the data returned is real protected health information, synthetic/demo data, or something else entirely. The lack of documentation makes it impossible to verify what the endpoint actually returns or what input it expects beyond a POST request.

Capabilities

x402-paymentusdc-settlementbase-networkhipaa-recordspay-per-requestno-api-keypost-method

Use cases

  • Retrieving HIPAA-related health record data on a per-request basis
  • Integrating health record lookups into agent workflows without API key management
  • Programmatic access to record ID 19 from a HIPAA records collection

Fit

Best for

  • Developers exploring x402 pay-per-call health data endpoints
  • Agent-based workflows needing keyless access to health records
  • Prototyping integrations that require on-demand medical record retrieval

Not for

  • Production HIPAA-compliant healthcare applications (compliance status is unverified)
  • Bulk or batch retrieval of large health record datasets (pay-per-request model)
  • Users who need detailed documentation or guaranteed SLAs

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/19 \
  -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 live (returns a valid 402 x402 challenge), but there is no documentation, no request/response schema, no examples, and the HIPAA records endpoint is not even listed on the provider's public catalog. The docs pages are empty. The HIPAA label raises regulatory concerns with zero supporting information.

Warnings

  • HIPAA-labeled endpoint with no documentation on data provenance, compliance, or whether data is real or synthetic
  • This specific endpoint (/api/v1/hipaa/records/19) is not listed among the provider's publicly advertised APIs
  • No request body schema or response schema available — input/output format is unknown
  • Docs, pricing, and README pages contain no useful content beyond a wallet connect prompt
  • Regulated health data category — verify compliance obligations before use

Citations

Provenance

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

Agent access