x402basequality 0.25

x402-gated compliance reports endpoint on Base, paid per-request in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to a compliance report (resource ID 87) via the x402 payment protocol. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind x402 micropayments on the Base network using USDC.

The specific endpoint `/api/v1/compliance/reports/87` accepts POST requests and returns JSON. Payment is settled on-chain on Base using USDC (contract 0x8335…2913) with an exact-scheme challenge. The maximum amount required per call is 20,000 base units of USDC, which at 6 decimals equals $0.02 USD. The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what a "compliance report" contains or what inputs the POST body expects. The endpoint is confirmed live (returns a valid x402 402 challenge), but the actual functionality behind the paywall is opaque.

Capabilities

x402-paymentusdc-micropaymentbase-networkcompliance-reportper-request-billingjson-response

Use cases

  • —Retrieving compliance report data (report ID 87) via a single micropayment
  • —Integrating on-chain pay-per-call compliance checks into automated agent workflows
  • —Accessing compliance information without API key registration

Fit

Best for

  • —Agents needing on-demand compliance data with no subscription overhead
  • —Developers experimenting with x402 micropayment-gated APIs
  • —Workflows requiring keyless, pay-as-you-go API access on Base

Not for

  • —Users who need detailed documentation or schema guarantees before integrating
  • —High-volume compliance screening where per-request costs add up
  • —Anyone needing compliance reports beyond the single resource ID 87

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the compliance report contains, what POST body is expected, or what the response schema looks like. No OpenAPI spec, no examples, and all doc pages are empty. The endpoint path references a single hardcoded report ID (87) with no explanation.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no content
  • —No OpenAPI or schema definition; request body and response format are completely unknown
  • —The endpoint path references a specific report ID (87); unclear if other IDs exist or what this report covers
  • —The term 'compliance report' is vague and could involve regulated data; verify suitability for your use case
  • —Platform appears to be a generic x402 demo/showcase with many endpoint categories but no substantive docs for any of them

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/KnWV2J
x402-gated compliance reports endpoint on Base, paid per-request in USDC. — Clawmart · Clawmart