x402basequality 0.35

Pay-per-call employee salary data endpoint on Base via x402, settled in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/employees/67/salary

What it does

This x402-enabled endpoint at lowpaymentfee.com returns salary information for a specific employee (ID 67) via a POST request. Payment is settled on the Base network using USDC (USD Coin) at a cost of $0.02 per request. The endpoint requires no API keys, no rate limits, and provides instant access — callers simply attach an x402 payment header to authorize each call.

The endpoint is part of a broader suite of pay-per-call APIs offered by lowpaymentfee.com spanning data & analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request. However, the specific endpoint being listed here (`/api/v1/employees/67/salary`) is not prominently featured on the provider's landing page among the advertised API categories. It appears to be a demo or sample resource. No OpenAPI schema, request body documentation, or response examples are available from the crawled material.

The endpoint is confirmed live: it returns a proper x402 version 1 challenge with a 402 status code, advertising payment to address `0x1A2B...85F3` using USDC on Base. The maximum amount required is 20,000 base units (i.e., $0.02 given USDC's 6 decimals). The payment timeout is 300 seconds.

Capabilities

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

Use cases

  • —Retrieving salary information for employee records in a pay-per-call model
  • —Demonstrating x402 payment protocol integration with a simple data endpoint
  • —Building payroll dashboards that pull salary data on demand

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents needing on-demand employee salary data without API key management
  • —Prototyping micropayment-gated data access patterns

Not for

  • —Bulk payroll data exports requiring thousands of records at once
  • —Production HR systems needing authenticated, role-based access control
  • —Users without USDC on the Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/employees/67/salary
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live via a valid x402 402 challenge, but there is no OpenAPI schema, no documented request/response format, no examples, and the specific employee salary endpoint is not listed among the provider's advertised APIs. The crawled docs/pricing/README pages returned only 'Connect wallet' with no substantive content.

Warnings

  • —No request body schema or response schema documented anywhere in crawled material
  • —The /api/v1/employees/67/salary path is not listed among the provider's advertised API endpoints — it may be a demo or undocumented resource
  • —All docs, pricing, README, and API pages returned minimal content ('Connect wallet') with no useful documentation
  • —No OpenAPI spec or ai-plugin manifest found

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-21 20:47:10Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/nk4r7a
Pay-per-call employee salary data endpoint on Base via x402, settled in USDC. — Clawmart · Clawmart