x402basequality 0.25

AML alerts endpoint with per-request USDC payment on Base via x402

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/12`. 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 use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/aml/alerts/12`) returns an x402 challenge requesting up to 20,000 base units of USDC (0.02 USD) per request. The platform advertises a flat $0.02/request pricing model across all its APIs with no API keys, no rate limits, and no minimum commitments. Payment is made via the x402 `exact` scheme, sending USDC to the specified payTo address on Base.

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. The endpoint path suggests it retrieves a specific AML alert by ID (12), but the actual data format and input parameters are unknown. The platform appears to be a generic x402 API marketplace, but without documentation it is difficult to assess the quality or source of the underlying data.

Capabilities

aml-alertsx402-paymentusdc-settlementbase-networkpay-per-requestanti-money-laundering

Use cases

  • Retrieving AML alert details for compliance workflows
  • Integrating AML screening into automated transaction pipelines
  • Querying specific suspicious activity alerts by ID
  • Adding AML checks to fintech or crypto applications

Fit

Best for

  • Developers needing low-cost, keyless AML alert data
  • Agents that can pay per-request via x402 on Base
  • Prototyping compliance integrations without subscription commitments

Not for

  • Production compliance systems requiring documented SLAs and audit trails
  • Users who need detailed API documentation and response schemas before integration
  • Regulated entities requiring vendor due diligence and certifications

Quick start

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

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 explanation of what AML alert data is actually returned. The AML alerts path does not appear on the provider's own homepage listing. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or JSON schema describing request parameters or response format
  • The /api/v1/aml/alerts/ path is not listed among the provider's advertised APIs on the homepage
  • AML/compliance data is a regulated category — no information about data sources, accuracy, or certifications is provided
  • Response content and data quality are completely unknown

Citations

Provenance

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

Agent access

AML alerts endpoint with per-request USDC payment on Base via x402 — Clawmart · Clawmart