AML alerts endpoint on Base, pay-per-call via x402 with 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/80`. It is part of a broader platform offering 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/80`) 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 requests and returns `application/json`. No API keys or rate limits are advertised; access is gated purely by 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 schema, no request/response examples, and no description of what the AML alerts data actually contains or what parameters the POST body accepts. The endpoint path includes an ID (`80`), suggesting it retrieves a specific alert record, but this is speculative. The platform advertises uniform $0.02 pricing across all endpoints.
Capabilities
Use cases
- —Retrieving AML alert details for compliance workflows
- —Integrating AML screening data into automated transaction monitoring pipelines
- —Agents querying specific AML alert records on-demand with micropayments
Fit
Best for
- —Developers needing on-demand AML alert data without API key management
- —Agent-based compliance workflows that can pay per call via x402
- —Low-volume or sporadic AML data lookups where subscription pricing is wasteful
Not for
- —High-volume AML screening requiring bulk or batch APIs with SLAs
- —Users who need detailed documentation or guaranteed schema stability before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/80 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"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 AML alert data is actually returned. The AML alerts endpoint is not even listed on the site's own landing page among its advertised APIs, raising questions about its completeness. This is effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content
- —No OpenAPI or request/response schema provided; request body format and response structure are unknown
- —The /api/v1/aml/alerts/80 endpoint is not listed among the site's advertised APIs, suggesting it may be experimental or incomplete
- —AML/compliance data may be subject to regulatory requirements — verify data provenance and licensing before relying on it
Citations
- —The endpoint returns an x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/aml/alerts/80
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/aml/alerts/80