x402basequality 0.30

Pay-per-call audit logs endpoint on Base via x402 — $0.02/request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/audit/logs/60

What it does

This endpoint at lowpaymentfee.com provides access to audit log data (specifically log entry 60) via the x402 payment protocol. It is part of a broader suite of pay-per-request APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints on the platform share a uniform $0.02-per-request pricing model settled in USDC on the Base network.

The specific endpoint `/api/v1/audit/logs/60` accepts POST requests and returns JSON. Payment is handled inline via the x402 protocol: callers attach an `X-PAYMENT` header containing a signed USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the provider's wallet on Base. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-call.

Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no description of what the audit log data actually contains. The endpoint is confirmed live (402 challenge returned), but the lack of documentation makes it difficult to know what payload to send or what response to expect.

Capabilities

x402-paymentusdc-settlementbase-networkaudit-logspay-per-requestno-api-key

Use cases

  • —Retrieving audit log records on a per-call payment basis
  • —Integrating pay-per-request audit data into agent workflows
  • —Accessing log data without API key registration

Fit

Best for

  • —Agents that need on-demand audit log access without subscription commitments
  • —Developers experimenting with x402 pay-per-call patterns on Base
  • —Use cases requiring keyless, permissionless API access

Not for

  • —Production systems requiring well-documented request/response schemas
  • —High-volume log retrieval where per-call pricing is inefficient
  • —Users who need detailed API documentation before integration

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/audit/logs/60 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-signed-payment-header>"

Endpoint

URLhttps://lowpaymentfee.com/api/v1/audit/logs/60
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 x402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no description of what audit log data is actually returned. This is effectively a stub listing.

Warnings

  • —No documentation available — /docs, /api, /pricing, and /README all return only a 'Connect wallet' prompt with no content.
  • —No OpenAPI or request/response schema provided; request body format and response structure are unknown.
  • —The specific meaning of 'audit/logs/60' (whether 60 is a log ID, category, or something else) is undocumented.
  • —The broader platform lists many endpoint categories (AI, finance, etc.) but none have visible documentation either.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/mMcMUU
Pay-per-call audit logs endpoint on Base via x402 — $0.02/request in USDC. — Clawmart · Clawmart