x402basequality 0.30

AML alerts endpoint paid per-request via x402 on Base (USDC).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to an AML (Anti-Money Laundering) alerts resource at `/api/v1/aml/alerts/4`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/aml/alerts/4`) costs up to $0.02 per request (maxAmountRequired of 20,000 base units of USDC with 6 decimals). Payment is made via the x402 `exact` scheme, requiring an `X-PAYMENT` header. The endpoint accepts POST requests and returns `application/json`. No API keys or rate limits are advertised; access is gated purely by micropayment.

Documentation is extremely sparse. The landing page lists available API categories and a uniform $0.02 pricing model, but the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The AML alerts endpoint itself is not listed on the homepage, making it unclear what data it returns or what input it expects beyond a POST body. The endpoint is live and responds with a valid 402 challenge.

Capabilities

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

Use cases

  • Retrieving AML alert data for compliance workflows
  • Integrating anti-money-laundering checks into automated pipelines
  • Querying specific AML alert records by ID

Fit

Best for

  • Developers needing on-demand AML alert data without API key management
  • Agents that can pay per-call via x402 on Base
  • Low-volume compliance queries where pay-per-use is preferred over subscriptions

Not for

  • High-volume AML screening requiring bulk pricing or SLAs
  • Users who need detailed API documentation and request/response schemas before integrating
  • Non-crypto-native consumers who cannot settle payments in USDC on Base

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The AML alerts endpoint is not even listed on the provider's homepage. It is essentially a stub listing with only pricing and protocol details confirmed.

Warnings

  • No API documentation available — docs, pricing, and API pages all render only 'Connect wallet' with no content.
  • No request or response schema is documented; input format and output structure are unknown.
  • The /api/v1/aml/alerts/4 endpoint is not listed among the provider's advertised APIs on the homepage.
  • AML/compliance data may be subject to regulatory requirements; verify data provenance and accuracy before relying on it.

Citations

Provenance

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

Agent access