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 AML (Anti-Money Laundering) alert data at the path `/api/v1/aml/alerts/99`. It is part of a broader platform offering dozens of pay-per-call 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/99`) returned a valid 402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per request. The platform advertises a flat $0.02/request pricing model with no API keys, no rate limits, and no minimum commitments. Payment is made inline via the X-PAYMENT header using the x402 exact scheme.

Documentation is extremely sparse — the docs, pricing, API, 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 (99), but the actual data schema and input parameters are unknown. The platform appears to be a generic x402 API storefront; the quality and depth of the underlying services cannot be verified from available materials.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestno-api-key

Use cases

  • Retrieving AML alert details by ID for compliance workflows
  • Integrating AML screening into automated financial pipelines
  • Agent-driven compliance checks with per-call crypto payment

Fit

Best for

  • Developers needing pay-per-call AML data without subscription commitments
  • AI agents that can settle payments via x402 on Base
  • Prototyping compliance integrations with low per-request cost

Not for

  • Production compliance systems requiring documented SLAs and audit trails
  • Users who need detailed API documentation and response schemas before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/99 \
  -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 402 challenge, confirming it is operational. However, there is no OpenAPI schema, no documentation beyond a wallet-connect prompt, no request/response examples, and no description of what the AML alerts endpoint actually returns. The listing is effectively a stub with pricing info only.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or output schema provided; request and response formats are unknown
  • The nature and source of AML alert data is completely undocumented
  • The endpoint path includes a hardcoded ID (99); it is unclear how to query other alerts
  • Platform appears to be a generic x402 storefront; quality of underlying data is unverifiable

Citations

Provenance

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

Agent access