x402basequality 0.25

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

The specific endpoint probed (`/api/v1/aml/alerts/65`) returns an x402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per request. The platform advertises a flat $0.02 per request across all its APIs, with no API keys, no rate limits, and no minimum commitments required. Payment is made inline via the X-PAYMENT header using the x402 exact scheme.

Documentation on the site is extremely sparse — 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 description of what the AML alerts endpoint actually returns. The endpoint path suggests it retrieves a specific AML alert by ID (65), but the actual data format and fields are unknown. The platform appears to be a generic x402 API storefront with many listed endpoints, but the lack of documentation makes it difficult to assess the quality or reliability of the underlying data.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestanti-money-laundering

Use cases

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

Fit

Best for

  • Agents needing on-demand AML alert data without API key registration
  • Pay-per-use compliance data access on Base/USDC
  • Lightweight integration of AML checks into crypto-native workflows

Not for

  • Production compliance systems requiring documented SLAs and audit trails
  • Use cases needing bulk AML data exports or streaming alerts
  • Users who need detailed API documentation before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/65 \
  -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 and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint actually returns. The site's docs pages are empty. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet' with no content
  • No OpenAPI or JSON schema describing request parameters or response format
  • The AML alerts endpoint path and data source are completely undocumented — data quality and provenance unknown
  • The endpoint path includes a hardcoded ID (65); it is unclear how to discover or enumerate other alert IDs
  • Platform lists many diverse API categories but provides no evidence of actual underlying data services

Citations

Provenance

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

Agent access

AML alerts endpoint with per-request x402 payment on Base via USDC. — Clawmart · Clawmart