Pay-per-call audit log access on Base via x402 — $0.02/request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to audit log data (specifically log ID 31) behind an x402 paywall. The provider operates a broad suite of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all settled on the Base network using USDC. Each call costs $0.02 (20,000 base units of USDC with 6 decimals).
The specific resource `/api/v1/audit/logs/31` is described as "Premium API Access" and accepts POST requests. It returns `application/json`. Payment is made via the x402 protocol: the endpoint returns a 402 challenge with payment parameters, and the caller includes an `X-PAYMENT` header with a signed payment to the specified address on Base. No API keys, rate limits, or upfront commitments are required — access is purely pay-per-use.
Note that this particular endpoint (`/audit/logs/31`) is not listed on the provider's public landing page among the advertised API categories. The landing page showcases analytics, AI, finance, and utility endpoints, all at $0.02/request. Documentation pages (`/docs`, `/pricing`, `/README`) returned minimal content (just a "Connect wallet" prompt), so detailed request/response schemas are unavailable. The endpoint is live and responding with a valid x402 challenge.
Capabilities
Use cases
- —Retrieving audit log entries on a per-request payment basis
- —Programmatic access to log data without subscription or API key management
- —Agent-driven data retrieval with automatic micropayment settlement on Base
Fit
Best for
- —Agents or services needing one-off audit log lookups without account setup
- —Developers wanting zero-commitment, pay-as-you-go API access
- —x402-compatible clients settling micropayments in USDC on Base
Not for
- —High-volume bulk log retrieval where per-call pricing becomes expensive
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —Non-crypto users who cannot settle payments on the Base network
Quick start
# 1. Send POST to get the 402 challenge
curl -X POST https://lowpaymentfee.com/api/v1/audit/logs/31
# Response: 402 with x402 challenge JSON
# 2. Construct and sign payment, then retry with X-PAYMENT header
curl -X POST https://lowpaymentfee.com/api/v1/audit/logs/31 \
-H "X-PAYMENT: <signed-payment-payload>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no documentation of request/response formats, and the specific audit/logs endpoint is not mentioned on the provider's landing page. Docs pages are effectively empty. The listing is largely inferred from the 402 challenge metadata.
Warnings
- —The endpoint /api/v1/audit/logs/31 is not listed among the provider's publicly advertised APIs — it may be internal, experimental, or undocumented.
- —Documentation pages (/docs, /pricing, /README) returned no meaningful content beyond a wallet-connect prompt.
- —No request body schema or response schema is available; callers must discover the expected format by trial.
- —The description 'Premium API Access' is generic and does not clarify what data this endpoint actually returns.
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base with maxAmountRequired of 20000 base units ($0.02).https://lowpaymentfee.com/api/v1/audit/logs/31
- —The provider advertises $0.02/request pricing with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/audit/logs/31