x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a compliance report (resource ID 58) via the x402 payment protocol. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, infrastructure utilities, and compliance. Each call is settled on the Base network using USDC (contract 0x8335…2913) with no API keys, no rate limits, and no subscriptions required.

The specific endpoint `/api/v1/compliance/reports/58` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The platform's landing page confirms a flat $0.02/request pricing model across all listed endpoints. Payment is made via the x402 exact scheme, with a 300-second timeout window.

Documentation on the site is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint path suggests it returns a compliance report by ID, but the exact fields, input parameters, and response structure are unknown. The platform appears to be a demonstration or early-stage deployment of x402-powered microservices.

Capabilities

x402-paymentusdc-settlementbase-networkcompliance-reportpay-per-requestno-api-keyjson-response

Use cases

  • Fetching compliance report data on a per-request payment basis
  • Integrating pay-per-call compliance checks into agent workflows
  • Accessing compliance information without API key registration

Fit

Best for

  • Agents needing one-off compliance report lookups without subscription overhead
  • Developers experimenting with x402 payment-gated APIs on Base
  • Workflows requiring keyless, pay-as-you-go data access

Not for

  • Production compliance workflows requiring documented schemas and SLAs
  • High-volume batch compliance reporting (no bulk discount or batch endpoint documented)
  • Users who need fiat-only payment rails

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The compliance report context is entirely opaque — we cannot confirm what data is returned or what inputs are accepted. This is effectively a stub listing.

Warnings

  • No OpenAPI spec or schema documentation available
  • Docs, pricing, API, and README pages all render only 'Connect wallet' with no content
  • The endpoint path '/api/v1/compliance/reports/58' is not listed on the platform's landing page among advertised APIs — it may be unlisted or experimental
  • Request body schema and response format are completely unknown
  • No SLA, rate limit, or uptime guarantees documented

Citations

Provenance

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

Agent access

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