AML alerts endpoint paid per-request via x402 on Base (USDC), $0.02/call.
What it does
This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data via a pay-per-request model using the x402 protocol. The specific resource `/api/v1/aml/alerts/13` returns JSON data related to AML alert ID 13. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request (20,000 base units with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider, lowpaymentfee.com, hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, the AML alerts endpoint is not listed on the provider's public landing page among the advertised API categories, which raises questions about its documentation status and intended use. The endpoint is confirmed live, returning a proper 402 challenge with x402 version 1.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what fields the AML alert response contains or what input parameters the POST body expects. Users should treat this as a minimally documented endpoint and test carefully before relying on it in production.
Capabilities
Use cases
- —Retrieving AML alert details for compliance workflows
- —Integrating AML alert data into automated transaction monitoring pipelines
- —Agent-driven compliance checks that pay per query without subscription
Fit
Best for
- —Developers needing on-demand AML alert data without API key management
- —AI agents performing compliance lookups with crypto micropayments
- —Low-volume or sporadic AML data consumers who prefer pay-per-use
Not for
- —High-volume AML screening requiring bulk or batch endpoints
- —Users who need detailed documentation and guaranteed SLAs
- —Organizations that cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/13 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, but there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the AML alerts path is not listed among the provider's advertised APIs. Effectively a stub listing.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —The /api/v1/aml/alerts/ path is not listed among the provider's publicly advertised APIs — it may be experimental or undocumented
- —All docs/pricing/README pages returned only 'Connect wallet' with no substantive content
- —No request body schema or response schema is known — POST input format is entirely unknown
- —AML/compliance data may be subject to regulatory requirements; verify data provenance and accuracy independently
Citations
- —Endpoint returns a valid x402 version 1 challenge with 402 status on POSThttps://lowpaymentfee.com/api/v1/aml/alerts/13
- —Payment is in USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base network, maxAmountRequired 20000 base units ($0.02)https://lowpaymentfee.com/api/v1/aml/alerts/13
- —Provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The AML alerts endpoint is not listed among the provider's publicly advertised API categorieshttps://lowpaymentfee.com