x402basequality 0.30

x402-gated compliance report endpoint on Base, pay-per-call with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/compliance/reports/76

What it does

This endpoint at lowpaymentfee.com provides access to a specific compliance report (ID 76) behind an x402 paywall. 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 maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

The provider lowpaymentfee.com hosts a broader catalog of pay-per-request APIs spanning data & analytics, AI/ML inference (sentiment, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, the specific endpoint being listed here (/api/v1/compliance/reports/76) is not explicitly mentioned in the provider's landing page catalog, so its exact content and schema are unclear.

The x402 challenge was successfully captured (HTTP 402 with valid accepts array), confirming the endpoint is live. Documentation pages (/docs, /pricing, /api, /README) all returned only a "Connect wallet" prompt with no substantive content, so there is no schema documentation, request/response examples, or detailed description of what the compliance report contains.

Capabilities

x402-paymentusdc-settlementbase-networkcompliance-reportpay-per-requestjson-response

Use cases

  • —Retrieving a specific compliance report (ID 76) on demand with micropayment
  • —Integrating compliance data into automated agent workflows via x402
  • —Paying per-request for compliance information without API key management

Fit

Best for

  • —Agents needing on-demand compliance data with crypto micropayments
  • —Developers experimenting with x402 payment protocol on Base
  • —Workflows requiring keyless, pay-as-you-go API access

Not for

  • —Users who need detailed documentation or schema guarantees before integrating
  • —Bulk compliance data retrieval (no batch endpoint documented)
  • —Users without USDC on Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/compliance/reports/76
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no request/response schema, and the specific compliance report endpoint is not listed in the provider's own catalog. All doc pages returned only 'Connect wallet' with no content.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all return only a wallet-connect prompt with no substantive content.
  • —The specific endpoint /api/v1/compliance/reports/76 is not listed in the provider's public API catalog; its purpose and output are unknown.
  • —No request body schema or response schema documented anywhere.
  • —The term 'compliance report' is vague — unclear what data is returned or its regulatory context.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 04:36:59Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/9NxneP
x402-gated compliance report endpoint on Base, pay-per-call with USDC. — Clawmart · Clawmart