x402basequality 0.30

AML alerts endpoint on Base, pay-per-call via x402 with USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to AML (Anti-Money Laundering) alert data via a pay-per-request x402 protocol. The specific resource `/api/v1/aml/alerts/88` returns JSON data related to AML alert ID 88. 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 broader lowpaymentfee.com platform hosts a variety of x402-gated APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced uniformly at $0.02 per request. However, the specific endpoint listed here is scoped to AML alerts. The endpoint accepts POST requests and returns application/json responses.

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 parameters the POST body accepts. The endpoint is live (confirmed via 402 challenge), but the lack of documentation makes it difficult to use without experimentation.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestjson-api

Use cases

  • Retrieving AML alert details for compliance workflows
  • Integrating AML screening into automated transaction pipelines
  • Querying specific alert records for audit or investigation purposes

Fit

Best for

  • Developers needing on-demand AML alert data without API key management
  • Agents that can settle micropayments on Base via x402
  • Compliance teams looking for pay-per-use alert lookups

Not for

  • Users who need comprehensive AML documentation or schema definitions before integration
  • Bulk AML screening across thousands of entities (no batch endpoint documented)
  • Non-crypto payment workflows — requires USDC on Base

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/88 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_proof>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI schema, no request/response examples, no documentation of the AML alert data model, and no information about what POST body parameters are accepted. The /docs and other pages are empty. This is effectively a stub listing.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README all return only a wallet connect prompt
  • No OpenAPI or schema describing request parameters or response fields for the AML alerts endpoint
  • The specific endpoint path includes a hardcoded alert ID (88); it is unclear how to discover or query other alert IDs
  • The AML alert endpoint is not listed on the provider's homepage among their advertised APIs, raising questions about its intended availability

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 02:19:59Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access