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/78`. It is part of a broader platform that offers dozens of pay-per-request 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/78`) returns an x402 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 `exact` scheme to a specified wallet address. The endpoint accepts HTTP POST and returns `application/json`. No API keys or rate limits are advertised; access is gated entirely by the x402 micropayment.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no explanation of what the AML alerts data contains or what parameters the POST body accepts. The endpoint path includes a numeric ID (78), suggesting it retrieves a specific alert record, but this is speculative. The platform's landing page confirms the $0.02 per-request pricing and lists the general API categories available.
Capabilities
Use cases
- —Retrieving AML alert details for compliance workflows
- —Integrating anti-money-laundering checks into automated pipelines
- —Querying specific AML alert records by ID for investigation
Fit
Best for
- —Developers needing on-demand AML alert data without API key management
- —Agents that can pay per-call via x402 on Base
- —Low-volume compliance lookups where pay-per-request is cost-effective
Not for
- —High-volume bulk AML screening (no documented batch endpoint)
- —Users who need detailed API documentation or request/response schemas before integrating
- —Non-crypto payment workflows (only USDC on Base is accepted)
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/78 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, confirming pricing and payment details. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no description of what AML alert data is actually returned. The listing is essentially a stub with only payment metadata confirmed.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No request body schema or response schema documented anywhere
- —The AML alerts endpoint is not listed on the site's landing page among the advertised APIs
- —Endpoint path includes a hardcoded ID (78); unclear if other IDs are valid or how to discover them
- —Regulated domain (AML/compliance) with zero documentation on data provenance or accuracy
Citations
- —The endpoint returns an x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/aml/alerts/78
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/aml/alerts/78
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs