x402basequality 0.25

Pay-per-call medical records API on Base via x402 — $0.02 per request in USDC.

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

What it does

This endpoint at `/api/v1/medical/records/81` is part of a broader suite of pay-per-call APIs hosted on lowpaymentfee.com. It is accessed via the x402 payment protocol, settling on the Base network using USDC. The x402 challenge confirms the endpoint is live and requires a payment of 20,000 base units of USDC (i.e., $0.02) per request.

The provider's landing page advertises a wide range of API categories — data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced uniformly at $0.02 per request. This specific endpoint appears under a "medical/records" path, but no documentation, schema, or sample payloads are available for it. The endpoint accepts HTTP POST and returns `application/json`. No API keys or rate limits are advertised; access is gated entirely by x402 micropayment.

Because no request or response schema is documented, and the medical records path suggests handling of sensitive health data, callers should exercise caution. There is no visible privacy policy, HIPAA disclosure, or data-handling documentation on the provider's site. The actual content returned by this endpoint is unknown — it may be synthetic/demo data or a placeholder.

Capabilities

x402-paymentusdc-basepay-per-callmedical-recordsjson-apino-api-keyhttp-post

Use cases

  • —Retrieving medical record data (record ID 81) via a single paid API call
  • —Demonstrating x402 micropayment integration for health-related data access
  • —Agent-driven workflows that need on-demand medical record lookups without API key provisioning

Fit

Best for

  • —Developers experimenting with x402 payment-gated APIs
  • —Agents that need keyless, pay-per-call access to structured data
  • —Prototyping micropayment flows on the Base network

Not for

  • —Production healthcare applications requiring HIPAA-compliant data handling
  • —Use cases needing documented request/response schemas or SLAs
  • —Bulk data retrieval — each call costs $0.02 with no batch endpoint documented

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/medical/records/81
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 for this specific endpoint — no request schema, no response schema, no examples, and no description of what data is returned. The 'medical/records' path raises regulatory concerns with no visible compliance documentation.

Warnings

  • —No request or response schema documented for this endpoint
  • —Path suggests medical/health data but no HIPAA, privacy policy, or data-handling disclosures are visible
  • —The provider site shows only 'Connect wallet' on /api, /pricing, and /README pages — effectively no documentation
  • —Endpoint may return synthetic or placeholder data; actual content is unknown
  • —This endpoint is one of many on a generic multi-category API platform — specificity of the medical records offering is unverified

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/6g372a
Pay-per-call medical records API on Base via x402 — $0.02 per request in USDC. — Clawmart · Clawmart