x402basequality 0.30

AML alerts endpoint with per-request x402 payment on Base network via USDC.

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

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/56` returns alert information in JSON format, gated behind a USDC micropayment on the Base network.

The endpoint accepts POST requests and charges a maximum of $0.02 per call (20,000 base units of USDC with 6 decimals). Payment is handled via the x402 exact scheme — no API keys, subscriptions, or rate limits are required. The broader lowpaymentfee.com platform advertises a wide catalog of similarly priced endpoints spanning data analytics, AI/ML inference, finance, crypto, and utility services, all at $0.02 per request.

Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the AML alert response contains. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual data quality and schema of the response body are unknown.

Capabilities

aml-alertspay-per-requestx402-paymentusdc-base-networkjson-responseno-api-key

Use cases

  • —Retrieving AML alert details for compliance workflows
  • —Integrating AML alert data into automated transaction monitoring pipelines
  • —Agent-driven compliance checks that pay per query without subscription overhead

Fit

Best for

  • —Developers needing on-demand AML alert data without API key management
  • —AI agents performing compliance lookups with crypto micropayments
  • —Low-volume or sporadic AML data consumers who prefer pay-per-use

Not for

  • —High-volume AML monitoring requiring bulk data exports or streaming
  • —Users who need detailed documentation and guaranteed SLAs before integration
  • —Organizations that cannot settle payments in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid x402 402 challenge, but there is no OpenAPI schema, no request/response examples, and all documentation pages are empty stubs. The AML alerts path is not even listed on the provider's own landing page catalog, making it unclear what data is actually returned. Effectively a stub listing.

Warnings

  • —No documentation available — all doc pages return only a wallet-connect prompt
  • —No OpenAPI or JSON schema describing request parameters or response format
  • —The /api/v1/aml/alerts/56 path is not listed in the provider's public API catalog, raising questions about its intended availability
  • —Response data quality and accuracy for AML alerts cannot be verified from available materials
  • —AML/compliance data may be subject to regulatory requirements — verify data provenance before relying on it

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/CbpG2n
AML alerts endpoint with per-request x402 payment on Base network via USDC. — Clawmart · Clawmart