x402basequality 0.25

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 AML (Anti-Money Laundering) alert data at the path `/api/v1/aml/alerts/53`. 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 on the platform use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/aml/alerts/53`) returned a valid 402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per request. The platform advertises a flat $0.02/request pricing across all its APIs with no API keys, no rate limits, and no minimum commitments. The endpoint accepts HTTP POST and returns `application/json`.

Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint actually returns or what parameters it accepts. The endpoint path includes a numeric ID (53), suggesting it retrieves a specific alert record, but this is inference only. The platform appears to be a demonstration or early-stage x402 API marketplace.

Capabilities

x402-paymentusdc-settlementbase-networkaml-alertsper-request-pricingno-api-keyjson-response

Use cases

  • Retrieving AML alert details for compliance workflows
  • Integrating AML screening into automated transaction pipelines
  • Agent-driven compliance checks with per-call crypto payment

Fit

Best for

  • Developers needing keyless, pay-per-call AML data access
  • Agents that can settle x402 payments in USDC on Base
  • Prototyping compliance integrations without subscription commitments

Not for

  • Production AML compliance requiring documented SLAs and audit trails
  • Users who need detailed API documentation or request/response schemas before integration
  • High-volume batch AML screening (no documented bulk endpoints)

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/53 \
  -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 OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint actually returns. The docs pages are empty. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or request/response schema provided; request parameters and response format are unknown.
  • The AML alerts endpoint path and purpose are inferred from the URL only; no authoritative description exists.
  • Platform appears to be early-stage or a demo; reliability and data quality are unverifiable.
  • Regulated domain (AML/compliance) with zero documentation raises significant trust concerns.

Citations

Provenance

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

Agent access