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/83` returns JSON data related to AML alert ID 83. 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 x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced at $0.02 per request. However, the specific endpoint being listed here falls under an AML alerts category that is not prominently documented on the provider's landing page. There is no OpenAPI schema, no request/response examples, and no detailed documentation available for this endpoint — the docs, pricing, and README pages all render only a wallet-connect prompt with no substantive content.
Because the endpoint is live (returns a well-formed 402 challenge) but lacks any documentation about what fields the AML alert response contains, what POST body parameters it expects, or how alert IDs are structured, consumers should treat this as a minimally documented endpoint. The x402 challenge confirms it is operational and accepts USDC on Base.
Capabilities
Use cases
- —Retrieving AML alert details for compliance workflows
- —Integrating AML screening data into automated transaction monitoring pipelines
- —Agent-driven compliance checks that pay per query without API key provisioning
Fit
Best for
- —Developers needing on-demand AML alert data without subscription commitments
- —AI agents performing compliance lookups with crypto-native payment
- —Low-volume or sporadic AML data consumers who prefer pay-per-call pricing
Not for
- —High-volume AML screening requiring bulk or batch endpoints
- —Users who need detailed API documentation and response schema guarantees before integration
- —Organizations that cannot settle payments in USDC on Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/83 \
-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 zero documentation on request parameters, response schema, or what AML alert data is actually returned. The AML alerts path is not listed on the provider's landing page among its advertised APIs, and all doc pages render only a wallet-connect stub. This is effectively a stub listing.
Warnings
- —No documentation available for the /api/v1/aml/alerts/ path — not listed among the provider's advertised endpoints
- —No request body schema or response schema documented anywhere
- —AML/compliance data may be subject to regulatory requirements; verify data provenance and licensing
- —Docs, pricing, and README pages return only a wallet-connect prompt with no content
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/aml/alerts/83
- —The provider advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/aml/alerts/83