x402basequality 0.35

Insurance claims data endpoint on Base, paid per-request via x402 in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to insurance claims data (specifically claim ID 16) behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance, crypto, infrastructure utilities, and more. All endpoints on the platform use the x402 protocol for payment, settling in USDC on the Base network.

The specific endpoint `/api/v1/insurance/claims/16` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0.02 USD per request), consistent with the platform's uniform $0.02/request pricing. Payment is made via the x402 "exact" scheme to a specified wallet address. No API keys are required; access is granted purely through the x402 payment header.

Documentation is minimal — the platform's landing page lists available endpoints and pricing but provides no request/response schemas, parameter descriptions, or example payloads. The insurance claims category is not listed on the homepage among the advertised API groups, so the exact data returned by this endpoint is unclear. The endpoint is confirmed live (returns 402 challenge as expected).

Capabilities

x402-paymentusdc-settlementbase-networkinsurance-claims-datapay-per-requestno-api-keyjson-response

Use cases

  • Retrieving insurance claim details programmatically with per-request payment
  • Integrating insurance data into agent workflows without subscription overhead
  • Demonstrating x402 protocol payment flows for data access

Fit

Best for

  • Agents needing on-demand insurance claims data without API key management
  • Developers experimenting with x402 micropayment protocols
  • Low-volume, pay-as-you-go data retrieval

Not for

  • High-volume insurance data pipelines where per-request costs add up
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • Production systems needing well-documented request/response schemas

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation on request parameters, response schema, or what insurance claims data is actually returned. The insurance category isn't even listed on the provider's homepage. Effectively a stub with confirmed liveness.

Warnings

  • No request or response schema documented — payload structure is unknown
  • Insurance claims endpoint not listed among the provider's advertised API categories on the homepage
  • No examples, parameter descriptions, or error documentation available
  • Unclear what data claim ID 16 represents or whether other claim IDs are accessible

Citations

Provenance

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

Agent access