x402basequality 0.30

AML alerts endpoint payable per-request via x402 on Base with 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/41`. It is part of a broader platform that offers dozens of pay-per-call API endpoints 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 probed (`/api/v1/aml/alerts/41`) is live and returns a valid x402 402 challenge. The price advertised in the challenge is 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The platform's landing page confirms a flat $0.02/request pricing model across all endpoints, 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 is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no additional technical content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the AML alerts endpoint actually returns. The endpoint path suggests it retrieves a specific AML alert by ID (41), but the actual response format and input parameters are unknown beyond the fact that it accepts POST requests and returns `application/json`.

Capabilities

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

Use cases

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

Fit

Best for

  • Developers needing low-cost, pay-per-call AML data without subscription commitments
  • Agents that can settle payments via x402 on Base using USDC
  • Prototyping compliance integrations with minimal onboarding friction

Not for

  • Production compliance systems requiring documented SLAs and guaranteed uptime
  • Users who need detailed API documentation and response schema before integration
  • Organizations requiring non-crypto payment methods

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on request parameters, response schema, or what AML alert data is actually returned. The docs/pricing/README pages are all empty beyond a wallet connect prompt. Without any schema or examples, this is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages all render only 'Connect wallet'
  • No OpenAPI spec or response schema provided; actual response format is unknown
  • The AML alerts endpoint is not listed on the provider's landing page among their advertised APIs, raising questions about its status
  • Compliance/AML data may be subject to regulatory requirements — verify data provenance and accuracy independently

Citations

Provenance

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

Agent access