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/6

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/6` is described by the provider 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).

The provider operates a broader platform offering dozens of x402-gated API endpoints across categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all uniformly priced at $0.02 per request. The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (docs, pricing, README) all resolve to a minimal "Connect wallet" prompt with no further technical detail, so the actual request/response schema for this HIPAA records endpoint is unknown.

Because this endpoint deals with HIPAA-labeled health records, consumers should exercise caution: there is no visible documentation explaining what data is returned, how PHI is handled, or whether the service is actually HIPAA-compliant. The endpoint is live (returns a valid 402 x402 challenge), but the lack of schema, examples, or compliance documentation is a significant gap.

Capabilities

x402-paymentusdc-basehipaa-recordsper-request-pricingpost-endpointno-api-key

Use cases

  • —Retrieving health record data on a per-request payment basis
  • —Integrating HIPAA-labeled records into agent workflows without API key management
  • —Programmatic access to medical record entries via crypto micropayment

Fit

Best for

  • —Developers needing on-demand health record access without subscription commitments
  • —Agent-based systems that can settle x402 payments in USDC on Base
  • —Prototyping integrations that require per-call billing for health data

Not for

  • —Production healthcare systems requiring verified HIPAA compliance documentation
  • —Use cases needing detailed API schemas, error handling docs, or SLAs
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is zero documentation on request/response schemas, no examples, and no compliance information despite the HIPAA label. Docs pages are empty stubs. This is effectively a stub listing.

Warnings

  • —Endpoint is labeled 'HIPAA' but no compliance documentation, BAA, or privacy policy is visible anywhere on the site.
  • —No request or response schema is documented — the actual data returned is unknown.
  • —All documentation pages (/docs, /pricing, /README) resolve to a minimal 'Connect wallet' page with no content.
  • —Health data endpoints may be subject to regulatory requirements (HIPAA, GDPR); verify compliance before use.

Citations

Provenance

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

Agent access

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