AML alerts endpoint paid per-request via x402 on Base (USDC).
What it does
This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data at the path `/api/v1/aml/alerts/72`. 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 endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint probed (`/api/v1/aml/alerts/72`) returns a 402 challenge requesting up to 20,000 base units of USDC (i.e., $0.02 per request, since USDC uses 6 decimals). Payment is made via the x402 `exact` scheme to a designated wallet address. The response MIME type is `application/json`. The endpoint accepts HTTP POST requests and is marked as discoverable.
The platform advertises a flat $0.02 per request across all its APIs, with no API keys, no rate limits, no minimums, and instant access. Documentation pages exist at `/docs`, `/pricing`, and `/api`, but all currently render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation available for the AML alerts endpoint specifically. The actual data returned by this endpoint (alert structure, fields, filtering options) is unknown from the available material.
Capabilities
Use cases
- —Retrieving AML alert data for compliance workflows
- —Integrating anti-money-laundering checks into fintech applications
- —Automated monitoring of flagged transactions or entities
- —Agent-driven compliance screening with per-call payment
Fit
Best for
- —Developers needing on-demand AML alert data without subscription commitments
- —AI agents that need pay-per-call compliance data
- —Prototyping compliance integrations with minimal setup
Not for
- —Production compliance systems requiring SLA guarantees and detailed documentation
- —Bulk AML screening where per-request pricing is cost-inefficient
- —Users who need detailed API documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/72 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint actually returns. The docs, pricing, and API pages all render only a wallet-connect prompt. The listing is effectively a stub with pricing info only.
Warnings
- —No documentation available — all doc pages render only 'Connect wallet' with no content
- —No OpenAPI or request/response schema provided for the AML alerts endpoint
- —Unknown response structure — the actual fields and data returned are not documented
- —The endpoint path includes a hardcoded ID (72); it is unclear if this is parameterized or fixed
- —The platform lists many API categories but the AML alerts endpoint is not listed on the homepage, raising questions about its status
Citations
- —The endpoint returns a 402 challenge requesting up to 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/aml/alerts/72
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/aml/alerts/72
- —Documentation pages at /docs, /pricing, /api render only 'Connect wallet'https://lowpaymentfee.com/docs