x402basequality 0.25

AML alerts endpoint payable per-request via x402 on Base 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/55`. 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/55`) returns a 402 challenge requesting up to $0.02 per request (20,000 base units of USDC with 6 decimals). The platform advertises uniform $0.02/request pricing across all its APIs with no API keys, no rate limits, and no minimum commitments. Payment is made inline via the X-PAYMENT header using the x402 exact scheme.

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 (55), suggesting it retrieves a specific alert record, but this is inference only. The lack of documentation makes it difficult to assess the actual utility or data quality of this endpoint.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestcompliance-data

Use cases

  • Retrieving AML alert details for compliance workflows
  • Integrating anti-money-laundering checks into fintech applications
  • Automated monitoring of flagged transactions

Fit

Best for

  • Developers needing pay-per-call AML data without subscription commitments
  • Agents that can settle USDC payments on Base via x402
  • Low-volume compliance lookups where per-request pricing is economical

Not for

  • Production compliance systems requiring documented SLAs and audit trails
  • Users who need detailed API documentation and request/response schemas before integration
  • High-volume AML screening where batch pricing would be more cost-effective

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/aml/alerts/55 \
  -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 documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no description of what the AML alerts endpoint returns or accepts. The listing is effectively a stub.

Warnings

  • No API documentation available — all doc pages render only 'Connect wallet'
  • No OpenAPI or request/response schema provided
  • The AML alerts endpoint path and functionality are entirely undocumented; actual data content is unknown
  • This endpoint appears to serve compliance/regulated data (AML) but provides no information about data sources, accuracy, or regulatory standing
  • The endpoint path includes a hardcoded ID (55), and it is unclear how to discover or query other alert IDs

Citations

Provenance

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

Agent access