x402basequality 0.30

AML alerts endpoint paid per-request via x402 on Base (USDC).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data at the path `/api/v1/aml/alerts/35`. It is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints use the x402 protocol for payment, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/aml/alerts/35`) returns a 402 challenge requesting up to 20,000 base units of USDC (i.e., $0.02 per request, since USDC uses 6 decimals). Payment is made via the x402 exact scheme with no API keys or rate limits required — callers simply attach an X-PAYMENT header with a valid payment proof. The endpoint accepts POST requests and returns `application/json`.

Documentation on the site is extremely thin. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the AML alerts data actually contains. The endpoint path includes an ID (`35`), suggesting it retrieves a specific alert record, but the request body schema and response format are entirely unknown from available materials.

Capabilities

x402-paymentusdc-settlementbase-networkaml-alertsper-request-pricingno-api-keyjson-response

Use cases

  • Retrieving AML alert details for compliance workflows
  • Integrating AML screening into automated transaction pipelines
  • Querying specific anti-money-laundering alerts by ID for audit purposes

Fit

Best for

  • Agents needing on-demand AML alert data without subscription commitments
  • Compliance teams wanting pay-per-use access to alert records
  • Developers prototyping AML integrations with minimal setup

Not for

  • Bulk AML screening requiring thousands of alerts per second (no documented batch endpoint)
  • Users who need detailed API documentation or response schema guarantees before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/35 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-proof>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI schema, no request/response examples, and no documentation beyond a landing page listing. The AML alerts endpoint is not even listed on the homepage's API catalog, and all doc pages are empty. The actual data returned is completely unknown.

Warnings

  • No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or JSON schema describing request body or response format.
  • The /api/v1/aml/alerts/35 endpoint is not listed among the advertised APIs on the homepage, raising questions about its status.
  • Response content and AML alert data structure are entirely unknown — integrate with caution.

Citations

Provenance

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

Agent access