x402basequality 0.30

HIPAA health records endpoint, pay-per-call via x402 on Base (USDC).

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/hipaa/records/90

What it does

This endpoint at lowpaymentfee.com provides access to HIPAA-related health records via a pay-per-request x402 protocol. The specific resource `/api/v1/hipaa/records/90` is accessed via HTTP POST and settles payments in USDC on the Base network. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (6 decimals), which equals $0.02 per request.

The broader lowpaymentfee.com platform hosts a variety of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced uniformly at $0.02 per request. The platform emphasizes simplicity: no API keys, no rate limits, no commitments, and instant access. Payment is handled entirely through the x402 payment header mechanism.

Important caveat: the endpoint is labeled "HIPAA records," which implies it deals with protected health information. However, no documentation, OpenAPI schema, or detailed description of the data returned is available. There is no evidence of BAA (Business Associate Agreement) provisions, compliance certifications, or any specifics about what health record data is actually served. The HIPAA label should be treated with caution until the provider supplies more detail.

Capabilities

x402-paymentusdc-basehipaa-recordspay-per-requesthttp-postno-api-key

Use cases

  • —Retrieving health record data on a per-request payment basis
  • —Integrating HIPAA-labeled records into agent workflows without API key management
  • —Programmatic access to health data settled via crypto micropayments

Fit

Best for

  • —Developers exploring x402 pay-per-call health data endpoints
  • —Agents needing on-demand health record lookups without subscription commitments
  • —Prototyping health data integrations with crypto-native payment rails

Not for

  • —Production healthcare systems requiring verified HIPAA compliance and BAA agreements
  • —Use cases needing detailed API documentation, schemas, or guaranteed SLAs
  • —Applications that cannot settle payments in USDC on Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/hipaa/records/90
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns 402 with a valid x402 challenge), but there is no OpenAPI schema, no documentation of request/response formats, no examples, and no information about what data is actually returned. The HIPAA label raises significant compliance concerns with zero supporting evidence of actual compliance. The crawl pages beyond the homepage returned only 'Connect wallet' with no useful content.

Warnings

  • —HIPAA-labeled endpoint with no evidence of actual HIPAA compliance, BAA, or certification
  • —No request or response schema available — unknown what data is returned
  • —No documentation beyond the homepage listing; /api, /pricing, and /README pages are empty
  • —Regulated health data category — verify compliance independently before use
  • —The specific endpoint /api/v1/hipaa/records/90 is not listed on the provider's homepage catalog

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/N6Tq2g
HIPAA health records endpoint, pay-per-call via x402 on Base (USDC). — Clawmart · Clawmart