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/33

What it does

This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data at the path `/api/v1/aml/alerts/33`. 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/33`) 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 to a designated wallet address. The response MIME type is `application/json`. The endpoint accepts HTTP POST requests.

Documentation beyond the landing page is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the AML alerts endpoint actually returns. The platform advertises no API keys, no rate limits, and instant access, but specifics about the AML data source, alert schema, or coverage are unknown.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestjson-response

Use cases

  • —Retrieving AML alert data for compliance workflows
  • —Integrating anti-money-laundering checks into fintech applications
  • —Automated monitoring of flagged transactions or entities
  • —Agent-driven compliance data retrieval with micropayments

Fit

Best for

  • —Developers needing on-demand AML alert data without API key management
  • —Agents that can settle x402 micropayments on Base
  • —Prototyping compliance integrations with low per-call cost

Not for

  • —Production compliance systems requiring documented SLAs and data provenance
  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —Non-crypto users who cannot settle USDC payments on Base

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what AML alert data is actually returned. The AML alerts path is not even listed on the landing page among the advertised APIs. This is effectively a stub listing.

Warnings

  • —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content.
  • —No OpenAPI or JSON schema describing request parameters or response format.
  • —The /api/v1/aml/alerts/33 path is not listed among the advertised APIs on the landing page, raising questions about whether it is a supported production endpoint.
  • —AML/compliance data is a regulated category — data provenance, accuracy, and coverage are completely undocumented.
  • —No information about the data source, update frequency, or geographic coverage of AML alerts.

Citations

Provenance

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

Agent access

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