PEP (Politically Exposed Persons) earnings data via pay-per-call x402 on Base.
What it does
This endpoint at lowpaymentfee.com provides access to PEP (Politically Exposed Persons) earnings data through the `/api/v1/finance/PEP/earnings` path. It is part of a broader suite of finance and Web3 APIs offered by the same provider, all settled via the x402 protocol on the Base network using USDC.
The endpoint accepts POST requests and returns JSON. Payment is handled inline via the x402 `X-PAYMENT` header — no API keys or account registration required. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…on Base), which equals $0.02 per request (USDC uses 6 decimals). This is consistent with the provider's site-wide flat pricing of $0.02 per call.
Documentation is extremely sparse. The provider's docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what fields the PEP earnings endpoint accepts or returns. The endpoint path suggests it returns earnings or financial disclosure data for politically exposed persons, but the exact input parameters and output format are unknown. Agents should treat this as a lightly-documented endpoint and test with exploratory calls.
Capabilities
Use cases
- —Retrieving earnings or financial disclosure data for politically exposed persons
- —Compliance screening workflows that need PEP financial information
- —Automated AML/KYC pipelines requiring PEP data lookups
Fit
Best for
- —Agents needing on-demand PEP financial data without API key management
- —Compliance automation requiring per-call payment with no subscription
- —Crypto-native workflows settling on Base L2 with USDC
Not for
- —Bulk PEP screening at scale (no documented batch endpoint)
- —Users who need detailed API documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/finance/PEP/earnings \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{}'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what PEP earnings data is actually returned. This is effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and API pages all render only a wallet-connect prompt with no content.
- —No OpenAPI or JSON schema describing request parameters or response format.
- —No example requests or responses available; input/output structure is entirely unknown.
- —PEP/earnings data may fall under regulated compliance data categories — verify data provenance and licensing before relying on it for AML/KYC decisions.
- —The specific endpoint /api/v1/finance/PEP/earnings is not listed on the provider's homepage among their advertised APIs, raising questions about its status.
Citations
- —The x402 challenge returns maxAmountRequired of 20000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base networkhttps://lowpaymentfee.com/api/v1/finance/PEP/earnings
- —Provider advertises flat $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompt with no substantive contenthttps://lowpaymentfee.com/docs