Insurance claims data endpoint on Base, pay-per-request via x402 with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to insurance claims data (specifically claim #76) via the x402 payment protocol. It accepts POST requests and returns JSON. 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, rate limits, or subscriptions are required — each call is individually paid for using the x402 payment header.
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 at $0.02 per request. This particular endpoint falls under an insurance claims category, though the site's landing page does not explicitly list it among its featured APIs. The exact schema of the returned claims data is not documented; the only confirmed output metadata is that the MIME type is application/json.
Because there is no OpenAPI spec, no request/response schema documentation, and no examples available, the precise fields expected in the POST body and the structure of the response are unknown. Agents should be prepared to experiment or contact the provider for details. The endpoint is confirmed live — it returns a valid x402 402 challenge with version 1 and a 300-second payment timeout.
Capabilities
Use cases
- —Retrieving insurance claim details programmatically
- —Integrating claims data into underwriting or risk assessment workflows
- —Automated auditing or reconciliation of insurance claims
Fit
Best for
- —Agents needing on-demand insurance claims data without subscription commitments
- —Developers prototyping insurance data integrations with minimal setup
- —Crypto-native applications that can pay per request in USDC on Base
Not for
- —Bulk retrieval of large claims datasets (pay-per-request model may be costly at scale)
- —Users who need detailed API documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/insurance/claims/76 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>"Endpoint
Quality
The endpoint is confirmed live with a valid x402 challenge, but there is no OpenAPI spec, no request/response schema, no examples, and the insurance claims endpoint is not even listed on the provider's landing page. The actual data returned is entirely unknown, making this effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /api/v1/insurance/claims/76 path is not listed among the provider's advertised APIs on the landing page — it may be a test or unlisted resource
- —Request body schema and response structure are completely undocumented
- —The endpoint references a specific claim ID (76); it is unclear whether other claim IDs are accessible or what the broader API surface looks like
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/insurance/claims/76
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/insurance/claims/76
- —All listed APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider's landing page lists APIs in Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categories but does not list an insurance claims endpointhttps://lowpaymentfee.com