x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

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/10` accepts POST requests and charges up to $0.02 per call in USDC on the Base network. Payment is handled inline via the x402 `X-PAYMENT` header — no API keys, accounts, or rate limits are required.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers dozens of APIs across data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. The HIPAA records endpoint is not listed on the site's public landing page, which raises questions about its completeness and intended audience. Documentation is essentially absent: the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content.

Because the endpoint deals with HIPAA-labeled health records, consumers should exercise caution. There is no documentation describing the data schema, compliance posture, or what record ID "10" represents. The x402 challenge is live and well-formed, confirming the endpoint is operational, but the lack of any input/output schema, example payloads, or compliance documentation makes it difficult to evaluate fitness for production use.

Capabilities

x402-paymentper-request-billingusdc-basehipaa-recordspost-endpointno-api-keyhealth-data

Use cases

  • Retrieving HIPAA health records on a per-request payment basis
  • Programmatic access to medical record data without subscription
  • Agent-driven health data retrieval with inline crypto payment

Fit

Best for

  • Developers needing on-demand HIPAA record access without API key management
  • AI agents that can settle x402 payments on Base
  • Prototyping health-data workflows with low per-call cost

Not for

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

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint works. However, there is zero documentation on request/response schemas, no examples, no OpenAPI spec, and the HIPAA label carries regulatory implications with no compliance information provided. The docs pages are empty stubs.

Warnings

  • Endpoint is labeled 'HIPAA' but no compliance documentation, BAA, or certification details are provided — use with extreme caution for any real health data.
  • No input or output schema is documented; request body format and response structure are unknown.
  • This specific endpoint (/api/v1/hipaa/records/10) is not listed on the provider's public landing page.
  • All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no useful content.
  • Regulated category (health/HIPAA) — verify provider compliance independently before use.

Citations

Provenance

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

Agent access