x402basequality 0.30

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

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

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/99` returns JSON data when a valid X-PAYMENT header is supplied. Payment is settled in USDC on the Base network.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this particular HIPAA records endpoint advertises a maxAmountRequired of 20,000 base units of USDC (6 decimals), which equals $0.02 — consistent with the site-wide pricing.

Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no description of what fields the HIPAA records response contains. The endpoint is live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what data is actually returned or what input the POST body expects. The HIPAA label raises regulatory concerns — callers should verify compliance before use.

Capabilities

x402-paymentusdc-basehipaa-recordsper-request-pricingno-api-keyjson-response

Use cases

  • —Retrieving HIPAA-compliant health records programmatically
  • —Agent-driven access to medical data with per-call micropayments
  • —Integrating health record lookups into automated workflows

Fit

Best for

  • —Developers needing on-demand HIPAA record access without subscription
  • —AI agents that can settle x402 payments on Base
  • —Applications requiring pay-as-you-go health data retrieval

Not for

  • —Production healthcare systems requiring verified HIPAA compliance documentation
  • —Users who need detailed API documentation and request/response schemas before integration
  • —High-volume batch retrieval where per-call pricing is inefficient

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it accepts USDC on Base at $0.02 per call. However, documentation is effectively nonexistent — no OpenAPI spec, no request/response schemas, no explanation of what data is returned. The HIPAA label without compliance documentation is a significant concern.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README all return only a wallet-connect prompt
  • —No request body schema or response schema documented; callers cannot know what to send or what they will receive
  • —Endpoint is labeled 'HIPAA' but no compliance certifications, BAA information, or regulatory documentation is provided
  • —The specific record ID '99' is hardcoded in the URL — unclear if this is a demo or a real record identifier

Citations

Provenance

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

Agent access

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