x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to an AML (Anti-Money Laundering) alerts resource at `/api/v1/aml/alerts/2`. It is part of a broader platform that offers dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled via the x402 protocol on the Base network using USDC.

The specific endpoint listed here accepts POST requests and returns JSON. Payment is handled inline: callers attach an X-PAYMENT header containing a signed USDC payment on Base. The x402 challenge advertises a maximum amount of 20,000 base units of USDC (6 decimals), which equals $0.02 per request — consistent with the site-wide flat pricing of $0.02/request. There are no API keys, no rate limits, and no subscription commitments; access is instant once payment is included.

Documentation on the site is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint actually returns or what input it expects. The endpoint is live (returns a valid 402 challenge), but the lack of documentation makes it difficult to know the exact request format or response structure without experimentation.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkper-request-pricingno-api-keyjson-response

Use cases

  • Querying AML alert data for compliance workflows
  • Integrating AML checks into automated financial pipelines
  • Agent-driven compliance screening with per-call crypto payment

Fit

Best for

  • Developers needing on-demand AML alert data without subscriptions
  • AI agents that can settle payments via x402/USDC on Base
  • Lightweight compliance checks where per-request pricing is preferred

Not for

  • Users who need detailed API documentation before integrating
  • High-volume AML screening where bulk pricing would be more economical
  • Teams requiring traditional API key or OAuth authentication

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI schema, no request/response examples, and no documentation beyond a generic title. The AML alerts endpoint is not even listed on the site's own landing page, and all doc pages render only 'Connect wallet'. The actual functionality is entirely opaque.

Warnings

  • No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or request/response schema provided for this endpoint
  • The /api/v1/aml/alerts/2 path is not listed among the site's advertised APIs, raising questions about its status
  • Request body format and response structure are completely unknown

Citations

Provenance

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

Agent access