AML alerts endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data via a pay-per-call x402 protocol. The specific resource `/api/v1/aml/alerts/23` returns JSON data related to AML alert ID 23. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of $0.02 per request (20,000 base units at 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 on the Base network. However, this specific endpoint falls under a compliance/AML category that is not prominently listed on the provider's landing page. The endpoint is live and returns a proper 402 challenge when called without payment.
Documentation is extremely sparse. The crawled docs, pricing, API, 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 detailed description of what the AML alerts endpoint actually returns. The endpoint's purpose and data format must be inferred entirely from its URL path and the x402 challenge metadata.
Capabilities
Use cases
- —Retrieving AML alert details for compliance workflows
- —Integrating AML screening data into automated transaction monitoring pipelines
- —Querying specific AML alerts by ID for audit or investigation purposes
Fit
Best for
- —Agents needing on-demand AML alert data without subscription commitments
- —Compliance automation pipelines that pay per query
- —Developers prototyping compliance integrations on Base/USDC rails
Not for
- —Bulk AML screening requiring thousands of lookups (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed SLAs before integrating
- —Non-crypto-native callers who cannot produce x402 payment proofs
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/23 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payment. However, there is no OpenAPI schema, no request/response examples, and no meaningful documentation — the docs pages are empty. The AML alerts path is not listed on the provider's own landing page, making its actual functionality uncertain. This is effectively a stub listing.
Warnings
- —No documentation available — all doc/pricing/API pages return only 'Connect wallet' with no content.
- —The /api/v1/aml/alerts/ path is not listed among the provider's advertised API categories, raising questions about whether this endpoint is fully supported.
- —No request or response schema is available; the data format returned by this endpoint is unknown.
- —AML/compliance data may be subject to regulatory requirements depending on jurisdiction.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/aml/alerts/23
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/aml/alerts/23