x402basequality 0.25

AML alerts endpoint on Base, pay-per-call via x402 with USDC.

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 at the path `/api/v1/aml/alerts/96`. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/aml/alerts/96`) returns an x402 challenge requesting up to 20,000 base units of USDC (i.e., $0.02 per request, since USDC uses 6 decimals). Payment is made via the `exact` scheme to a specified wallet address. The endpoint accepts HTTP POST 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/request price, but the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. 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 its exact functionality unclear — it may return compliance alert data for a specific entity or transaction ID (the `96` in the path likely being an alert identifier).

Capabilities

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

Use cases

  • Retrieving AML alert details for compliance workflows
  • Integrating automated AML checks into fintech applications
  • Querying specific anti-money-laundering alerts by ID for audit trails

Fit

Best for

  • Developers needing on-demand AML alert data without API key management
  • Agents that can pay per request via x402 on Base
  • Compliance teams wanting programmatic access to alert records

Not for

  • Users who need detailed API documentation or schemas before integrating
  • Bulk AML screening requiring batch endpoints or subscription pricing
  • Production compliance systems that require SLA guarantees and support

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, no examples, and the AML alerts endpoint is not even listed on the provider's homepage. Functionality must be entirely inferred from the URL path.

Warnings

  • No OpenAPI spec or schema documentation available
  • The /api/v1/aml/alerts/96 endpoint is not listed on the provider's homepage — its existence and purpose are unverified beyond the x402 challenge
  • Docs, pricing, API, and README pages all render only 'Connect wallet' with no useful content
  • No request body schema or response schema documented; integration requires guesswork
  • AML/compliance data may be subject to regulatory requirements — verify data provenance and accuracy independently

Citations

Provenance

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

Agent access