x402basequality 0.25

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

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

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/78` is described generically as "Premium API Access" and accepts POST requests. Payment is settled in USDC on the Base network at $0.02 per request (20,000 base units of USDC with 6 decimals). No API keys or rate limits are advertised; access is gated entirely by the x402 payment header.

The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced uniformly at $0.02 per call. However, the specific HIPAA records endpoint is not listed on the provider's public landing page among the advertised API categories. Documentation pages (/docs, /pricing, /README) returned only a "Connect wallet" prompt with no substantive content, so the exact schema of request bodies and response payloads for this endpoint is unknown.

Because this endpoint claims to serve HIPAA-regulated health records, consumers should exercise caution. There is no visible documentation describing what data is returned, what compliance certifications the provider holds, or what the record ID "78" represents. The endpoint is live (returns a valid 402 challenge), but the lack of documentation and the sensitive regulated domain warrant significant caution.

Capabilities

x402-paymentusdc-base-networkhipaa-recordspay-per-requestno-api-keypost-method

Use cases

  • —Retrieving HIPAA health record data on a per-request payment basis
  • —Agent-driven access to medical records without pre-registration or API keys
  • —Programmatic health data retrieval settled in USDC on Base

Fit

Best for

  • —Developers needing on-demand access to health record data without subscription commitments
  • —AI agents that can settle x402 micropayments on Base
  • —Prototyping integrations that require HIPAA-related data access

Not for

  • —Production healthcare systems requiring verified HIPAA compliance certifications and BAAs
  • —Users who need detailed API documentation and response 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/78 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on request/response schemas, no OpenAPI spec, and the docs pages are empty. The HIPAA health-records domain is highly regulated, yet no compliance information is provided. The specific endpoint is not even listed on the provider's own landing page.

Warnings

  • —HIPAA-regulated health data: no compliance certifications, BAA, or privacy documentation visible
  • —Endpoint /api/v1/hipaa/records/78 is not listed among the provider's publicly advertised APIs
  • —All documentation pages (/docs, /pricing, /README) returned no substantive content
  • —No request or response schema available — input/output format is entirely unknown
  • —The meaning of record ID '78' is unexplained

Citations

Provenance

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

Agent access

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