x402basequality 0.25

HIPAA health records endpoint payable per-request via x402 on Base (USDC).

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

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/48` returns JSON data when a valid X-PAYMENT header is supplied. Payment is settled on the Base network using USDC (contract 0x8335…2913) with an exact-scheme challenge.

The x402 challenge advertises a maxAmountRequired of 20,000 base units. Since USDC uses 6 decimals, this translates to $0.02 per request — consistent with the provider's site-wide flat pricing of $0.02/request across all endpoints. The provider advertises no API keys, no rate limits, and instant access. The endpoint accepts POST requests and is marked as discoverable.

Important caveats: the endpoint name references "HIPAA records," which implies protected health information. However, the crawled site provides virtually no documentation about what data is actually returned, what input the POST body expects, or how HIPAA compliance is maintained. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no example requests or responses, and no information about the data source or compliance posture. Treat this endpoint with caution, especially given the regulated nature of health data.

Capabilities

x402-paymentper-request-billingusdc-settlementbase-networkhipaa-recordsjson-responsepost-method

Use cases

  • —Retrieving specific HIPAA-related health records on demand
  • —Integrating health data into agent workflows with per-call crypto payment
  • —Accessing medical record data without API key registration

Fit

Best for

  • —Developers needing on-demand health record access with crypto micropayments
  • —Agent-based systems that settle per-call via x402 on Base
  • —Prototyping health data integrations without subscription commitments

Not for

  • —Production healthcare systems requiring verified HIPAA compliance documentation
  • —Users who need detailed API documentation or OpenAPI specs before integration
  • —Non-crypto users who cannot settle payments on the Base network

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02/request in USDC on Base). However, there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the HIPAA health-data claim is entirely unsubstantiated. Docs pages return only wallet-connect prompts.

Warnings

  • —Endpoint claims to serve HIPAA records but provides no documentation on compliance, data provenance, or privacy safeguards
  • —No request body schema or response schema available — unknown what POST body is expected
  • —All documentation pages (docs, pricing, API, README) render only a 'Connect wallet' prompt with no content
  • —Regulated health data category — verify compliance independently before use
  • —The specific record ID '48' is hardcoded in the URL; unclear how to query other records

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/Z2baHd
HIPAA health records endpoint payable per-request via x402 on Base (USDC). — Clawmart · Clawmart