x402basequality 0.35

Pay-per-call employee salary data endpoint on Base via x402 (USDC).

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com returns employee salary information for a specific employee (ID 180) via a POST request. It is part of a broader platform offering dozens of pay-per-call API endpoints across data/analytics, AI/ML, finance/Web3, and infrastructure categories, all settled on the Base network using USDC.

The endpoint charges a maximum of $0.02 per request (20,000 base units of USDC with 6 decimals). Payment is handled via the x402 protocol: callers include an X-PAYMENT header with a signed payment proof, and the server verifies it before returning the response. No API keys, subscriptions, or rate limits are advertised — access is purely pay-per-use.

The specific endpoint `/api/v1/employees/180/salary` is not listed on the provider's landing page among the advertised API categories (analytics, AI, finance, infrastructure), so its exact response schema and data source are unknown. The probe confirms it is live and returns a valid x402 challenge with version 1, accepting the "exact" payment scheme on Base mainnet. The payTo address is `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` and the accepted asset is USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). Documentation pages beyond the landing page returned only a "Connect wallet" prompt with no additional technical detail.

Capabilities

x402-paymentusdc-settlementbase-networkemployee-salary-datapay-per-requestno-api-key

Use cases

  • Retrieving salary information for a specific employee on demand
  • Integrating pay-per-call payroll data into agent workflows
  • Demonstrating x402 micropayment protocol usage on Base

Fit

Best for

  • Agents needing on-demand employee salary data without subscriptions
  • Developers experimenting with x402 payment protocol on Base
  • Low-volume, pay-as-you-go data retrieval

Not for

  • Bulk payroll data exports across many employees
  • Use cases requiring detailed API documentation or guaranteed SLAs
  • Users without a Base-network USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/employees/180/salary \
  -H "X-PAYMENT: <x402-payment-proof>" \
  -H "Content-Type: application/json"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no OpenAPI schema, no documented request/response format, and the specific employee salary endpoint is not listed among the provider's advertised APIs. Documentation pages are empty beyond a wallet-connect prompt. The actual data returned is unknown.

Warnings

  • The endpoint /api/v1/employees/180/salary is not listed among the provider's advertised APIs — its data source and accuracy are unverifiable.
  • All documentation pages (docs, api, pricing, README) returned only a 'Connect wallet' prompt with no technical content.
  • No request body schema or response schema is available; callers must discover the format experimentally.
  • The employee salary data context raises potential privacy/compliance concerns depending on jurisdiction.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:04:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-23

Agent access

Pay-per-call employee salary data endpoint on Base via x402 (USDC). — Clawmart · Clawmart