x402basequality 0.30

HIPAA records endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to HIPAA records via a pay-per-request x402 payment protocol. The specific resource `/api/v1/hipaa/records/11` is labeled "Premium API Access" and accepts POST requests, settling payments in USDC on the Base network. The price per call is $0.02 (20,000 base units of USDC with 6 decimals), consistent with the provider's uniform pricing across all their API endpoints.

The provider lowpaymentfee.com hosts a broad catalog of x402-gated APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints share the same $0.02/request pricing with no API keys, no rate limits, and no minimum commitments. Payments are made via the x402 exact-payment scheme on the Base L2 network using USDC (contract 0x8335…2913).

Notably, this specific endpoint references "HIPAA records," which implies it handles or returns health-related data subject to HIPAA regulations. However, the crawled documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further detail. There is no OpenAPI schema, no request/response examples, and no documentation explaining what data the HIPAA records endpoint actually returns or what input it expects. The nature and authenticity of the health data served is entirely unclear from available materials.

Capabilities

x402-paymentusdc-settlementbase-networkhipaa-recordspay-per-requestpost-method

Use cases

  • Retrieving HIPAA-related health records programmatically with per-call payment
  • Agent-driven access to health data without API key provisioning
  • Integrating pay-as-you-go health record lookups into automated workflows

Fit

Best for

  • Developers needing on-demand access to health records with no subscription
  • AI agents that can settle x402 payments on Base in USDC
  • Prototyping health data integrations with minimal setup

Not for

  • Production healthcare applications requiring verified HIPAA compliance and BAAs
  • Users who need detailed API documentation or OpenAPI schemas before integration
  • High-volume use cases where per-request pricing may not be cost-effective

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear at $0.02/request in USDC on Base. However, there is zero documentation on request format, response schema, or what data is actually returned. The HIPAA label raises significant regulatory concerns with no supporting compliance information. Docs pages are empty beyond a wallet-connect prompt.

Warnings

  • Endpoint claims to serve HIPAA records but no compliance documentation, BAA, or privacy policy is available
  • No OpenAPI schema, request examples, or response examples are provided anywhere in the crawled material
  • All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no usable content
  • The nature, source, and authenticity of the health data served is completely unknown
  • Using health data APIs without verified HIPAA compliance may carry legal and regulatory risk

Citations

Provenance

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

Agent access