x402basequality 0.25

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/11`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/aml/alerts/11`) returned a live 402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per request. The platform advertises a flat $0.02/request pricing across all its APIs with no API keys, no rate limits, and no minimum commitments. Payment is made via the x402 `exact` scheme, sending USDC to the specified payTo address on Base.

Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The AML alerts endpoint is not listed on the homepage's API catalog, which raises questions about whether it is a fully supported production endpoint or a test/demo route. Without documentation on what request body to send or what response shape to expect, integration requires experimentation.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestno-api-key

Use cases

  • Retrieving AML alert data for a specific entity or transaction
  • Integrating compliance checks into automated financial workflows
  • Agent-driven AML monitoring with per-call crypto payment

Fit

Best for

  • Developers needing on-demand AML alert lookups without subscription commitments
  • AI agents that can pay per-request via x402/USDC on Base
  • Prototyping compliance integrations with minimal setup

Not for

  • Production compliance workflows requiring documented SLAs and audit trails
  • Users who need detailed API documentation and response schemas before integrating
  • High-volume AML screening where per-request pricing may not be cost-effective compared to bulk plans

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is zero documentation on request format, response schema, or what 'alerts/11' represents. The AML alerts path is not listed in the site's own API catalog, and all doc pages are empty. This is effectively a stub listing.

Warnings

  • No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
  • No OpenAPI spec or request/response schema provided
  • The /api/v1/aml/alerts/11 endpoint is not listed on the homepage API catalog, raising questions about its status
  • AML/compliance data may be subject to regulatory requirements — verify data provenance and accuracy independently

Citations

Provenance

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

Agent access

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