x402basequality 0.25

AML alerts endpoint with per-request x402 payment on Base (USDC).

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

What it does

This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data via a pay-per-request model using the x402 protocol. The specific resource `/api/v1/aml/alerts/25` returns alert data in JSON format, charged at $0.02 per request in USDC on the Base network. No API keys or rate limits are required; callers simply attach an x402 payment header to authenticate and pay in a single step.

The broader lowpaymentfee.com platform advertises a wide catalog of endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced uniformly at $0.02 per call. However, the AML alerts endpoint is not listed on the site's public catalog, and no documentation beyond the x402 challenge was found. The endpoint's exact input schema (what POST body fields it expects) and output schema (what fields the alert response contains) are undocumented. The crawled docs, pricing, API, and README pages all returned only a "Connect wallet" stub with no substantive content.

Because of the lack of documentation, callers should treat this endpoint experimentally. The x402 challenge confirms the endpoint is live and accepting payment negotiations, but without request/response examples or field-level documentation, integration requires trial and error.

Capabilities

aml-alertsx402-paymentusdc-basepay-per-requestjson-response

Use cases

  • —Retrieving AML alert details for compliance workflows
  • —Integrating real-time AML alerts into transaction monitoring dashboards
  • —Agent-driven compliance checks that pay per query with no API key

Fit

Best for

  • —Developers needing on-demand AML alert data without subscription commitments
  • —AI agents that can settle micropayments via x402 on Base
  • —Compliance teams exploring pay-per-use alert retrieval

Not for

  • —Production compliance systems requiring documented SLAs and guaranteed uptime
  • —Bulk AML data exports or batch processing (single-alert endpoint)
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The x402 challenge confirms the endpoint is live and reveals pricing and network details, but there is zero documentation on request/response schemas, no OpenAPI spec, no examples, and the AML alerts path is not even listed in the site's own catalog. Docs pages are empty stubs. This is effectively a stub listing.

Warnings

  • —No request or response schema documented — input fields for the POST body are unknown
  • —The /api/v1/aml/alerts/25 path is not listed in the site's public API catalog; its provenance is unclear
  • —All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' stub with no content
  • —AML/compliance data may be subject to regulatory requirements; verify data source legitimacy before relying on it

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/Cgg2dT
AML alerts endpoint with per-request x402 payment on Base (USDC). — Clawmart · Clawmart