Insurance claims data endpoint on Base, pay-per-request via x402 with USDC.
What it does
This x402-enabled endpoint at lowpaymentfee.com serves insurance claims data (specifically claim ID 74) behind a micropayment wall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The price per request is $0.02 (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid 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 its featured API groups. No OpenAPI schema, request/response examples, or detailed documentation were found for this specific endpoint, so the exact request body format and response structure are unknown.
Because the endpoint returned a well-formed 402 challenge with x402 version 1, it is confirmed live and accepting payments. However, the lack of documentation about what fields the claims endpoint expects or returns means callers will need to experiment or contact the provider for integration details.
Capabilities
Use cases
- —Retrieving insurance claim details programmatically with per-call payment
- —Integrating insurance claims data into automated workflows without subscription commitments
- —Agent-driven lookups of specific insurance claim records
Fit
Best for
- —Developers needing on-demand insurance claims data without API key management
- —AI agents that can settle USDC micropayments on Base
- —Low-volume or sporadic access to claims information
Not for
- —Bulk retrieval of large insurance datasets (pay-per-request at $0.02 adds up)
- —Users who cannot transact in USDC on the Base network
- —Applications requiring detailed schema documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/insurance/claims/74 \
-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 schema, no request/response examples, and no documentation specific to the insurance claims endpoint. The endpoint is not even listed on the provider's own landing page, making it effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /api/v1/insurance/claims/ path is not listed among the provider's advertised API categories
- —Request body format and response structure are completely unknown — callers must experiment
- —Provider pages (/api, /pricing, /README) returned only a 'Connect wallet' prompt with no useful content
Citations
- —Endpoint returns a valid x402 version 1 challenge with 402 statushttps://lowpaymentfee.com/api/v1/insurance/claims/74
- —Payment is in USDC (USD Coin) on the Base network, asset contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/insurance/claims/74
- —maxAmountRequired is 20000 base units (= $0.02 USDC)https://lowpaymentfee.com/api/v1/insurance/claims/74
- —Provider advertises $0.02/request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com