x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/aml/alerts/18

What it does

This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data at the path `/api/v1/aml/alerts/18`. 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/18`) is listed under the title "Premium API Access" and returned a live 402 challenge. The maximum amount required is 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The platform advertises uniform $0.02/request pricing across all its APIs, with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint actually returns. The endpoint path suggests it retrieves a specific AML alert by ID (18), but the actual payload structure, required POST body fields, and response format are unknown.

Capabilities

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

Use cases

  • —Retrieving AML alert details for compliance workflows
  • —Integrating anti-money-laundering checks into fintech applications
  • —Automated compliance monitoring for crypto transactions

Fit

Best for

  • —Developers needing on-demand AML alert data without subscription commitments
  • —Agents that can pay per-call via x402 on Base
  • —Low-volume compliance lookups where $0.02/request is cost-effective

Not for

  • —Production compliance systems requiring documented SLAs and guaranteed uptime
  • —Use cases needing detailed API documentation and request/response schemas before integration

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/aml/alerts/18
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base). However, there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the AML alerts endpoint actually returns. The docs pages are empty. This is effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no technical content
  • —No OpenAPI or JSON schema describing request body or response format
  • —The AML alerts endpoint purpose and data model are entirely undocumented
  • —AML/compliance data may be subject to regulatory requirements — verify data provenance and accuracy independently
  • —Cannot confirm what data is actually returned by this endpoint

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/7d85Pq
AML alerts endpoint payable per-request via x402 on Base (USDC). — Clawmart · Clawmart