Insurance claims data endpoint on Base, paid per-request via x402 in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to insurance claims data (specifically claim ID 99) via a POST request, gated by the x402 payment protocol. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider lowpaymentfee.com hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services, all priced uniformly at $0.02 per request. This particular endpoint falls under an insurance claims category, though the provider's landing page does not list it among the featured APIs, and no documentation, request/response schema, or example payloads are published for it. The endpoint is confirmed live: it returns a proper 402 challenge with x402 version 1 when called without payment.
Because no OpenAPI spec, input schema, or sample responses are available, callers will need to experiment with POST body formats. The output MIME type is declared as application/json. The payment timeout is 300 seconds. The payTo address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 and the USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base mainnet.
Capabilities
Use cases
- —Retrieving insurance claim details by ID
- —Integrating insurance claims data into automated workflows
- —Agent-driven insurance claim lookups with micropayments
Fit
Best for
- —Developers needing on-demand insurance claims data without subscription commitments
- —AI agents that can settle x402 payments on Base
- —Prototyping insurance data integrations with low per-call cost
Not for
- —Bulk retrieval of large insurance datasets (pay-per-request model adds up)
- —Users who need detailed API documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/insurance/claims/99 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, but there is no OpenAPI spec, no request/response schema, no documentation, and no examples. The insurance claims endpoint is not even listed on the provider's own landing page. Callers must guess at the POST body format. Pricing is clear ($0.02/request in USDC on Base).
Warnings
- —No request or response schema is documented — callers must discover the expected POST body by experimentation.
- —This specific endpoint (/api/v1/insurance/claims/99) is not listed among the provider's advertised APIs on the landing page.
- —No OpenAPI spec, README, or detailed docs are available; /README, /pricing, and /api pages all just show 'Connect wallet'.
- —Insurance data may be subject to regulatory requirements (HIPAA, state insurance regulations) depending on jurisdiction and data contents.
Citations
- —Endpoint returns a 402 challenge with x402 version 1, accepting USDC on Base with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/insurance/claims/99
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/insurance/claims/99
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The insurance claims endpoint is not listed among the provider's featured APIs on the landing pagehttps://lowpaymentfee.com