x402basequality 0.25

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 protocol. The specific resource `/api/v1/hipaa/records/63` is part of a broader platform that offers dozens of API endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

Payment is handled entirely through the x402 protocol: callers send a POST request, receive a 402 challenge with payment details, and include an `X-PAYMENT` header to settle. No API keys, accounts, or rate limits are advertised. The x402 challenge specifies a `maxAmountRequired` of 20,000 base units of USDC (6 decimals), which equals $0.02. The payment address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` and the USDC contract on Base is `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`.

Important caveats: the endpoint is labeled "HIPAA records," which implies it handles protected health information. However, there is no documentation, schema, or example response available to verify what data is actually returned, what input is expected, or whether any real HIPAA compliance measures are in place. The crawled docs, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. Agents should exercise extreme caution before sending payments to this endpoint, especially given the healthcare data implications and total lack of documentation.

Capabilities

x402-paymentusdc-settlementbase-networkhipaa-recordspay-per-requestno-api-key

Use cases

  • Retrieving HIPAA-related records on a per-request payment basis
  • Programmatic access to health data without API key management
  • Agent-driven healthcare data retrieval settled in USDC on Base

Fit

Best for

  • Developers needing keyless, pay-per-call access to health records
  • AI agents with Base USDC wallets requiring healthcare data
  • Prototyping x402-based healthcare data workflows

Not for

  • Production healthcare applications requiring verified HIPAA compliance documentation
  • Users who need detailed API documentation or response schemas before integrating
  • Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/hipaa/records/63
# Returns 402 with x402 challenge. Include X-PAYMENT header with valid payment proof to access.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is zero documentation on request/response schemas, no examples, no OpenAPI spec, and the docs/pricing/README pages are all empty. The HIPAA label raises serious compliance concerns with no supporting evidence of actual compliance.

Warnings

  • Endpoint claims to serve HIPAA records but no documentation exists to verify actual HIPAA compliance or data handling practices.
  • No request or response schema is available — it is unknown what data this endpoint returns or what input it expects.
  • All documentation pages (docs, pricing, README, api) returned only a 'Connect wallet' prompt with no content.
  • Healthcare/regulated data category: exercise extreme caution before sending payment or relying on this endpoint for real health information.
  • The specific record ID '63' in the URL is hardcoded; it is unclear whether other record IDs are available or how to discover them.

Citations

Provenance

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

Agent access