x402basequality 0.35

x402 micropayment-gated agent endpoint on Base (USDC) via LNPay/AIsa marketplace

Price
0.01 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint is part of the LNPay/AIsa AI Services Marketplace, a platform offering per-call micropayment services for AI agents. The specific resource at `/x402/agent` is protected by an x402 payment challenge and accepts USDC payments on the Base network. The challenge advertises a maximum cost of 10,000 units of USDC (the asset at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which is Base USDC with 6 decimals, so roughly $0.01 per call) paid to address 0x66FA4D79cA84016b42352BE33C908Dd812952Ec8.

The broader LNPay marketplace organizes services into categories including Content & Knowledge, Data & API Services, Compute & GPU Resources, Model Tokens & AI APIs, SaaS & Workflow Tools, Financial & Payment Services, Developer & Open-Source Agents, and AI Search & Retrieval APIs. The platform also offers an AIsa Payment SDK supporting multi-chain payments (Lightning, Solana, Base, BNB, Polygon, Stripe), an AIsa Twitter API for pay-per-call Twitter data, and an AIsa Treasury for multi-chain liquidity management.

Documentation for this specific endpoint is sparse. The x402 challenge's outputSchema names the resource "AgentPayWall-402-base" and indicates it is discoverable via HTTP GET, but no further details about request parameters, response format, or the exact nature of the protected resource are available from the crawled material. The generic description "Access to protected resource" does not clarify what data or service is returned after payment.

Capabilities

x402-payment-challengeusdc-base-micropaymentagent-paywallper-call-billingmulti-chain-marketplace

Use cases

  • AI agents paying per-call to access a gated resource on Base using USDC
  • Demonstrating x402 protocol payment flows for agent-to-service transactions
  • Integrating micropayment-gated services into autonomous agent workflows

Fit

Best for

  • AI agents with Base USDC wallets needing pay-per-call access
  • Developers exploring x402 micropayment protocol integrations
  • Autonomous agents operating on the Base L2 network

Not for

  • Users needing detailed API documentation before integration
  • Applications requiring free or subscription-based access without per-call payments
  • Use cases needing guaranteed SLAs or well-documented response schemas

Quick start

# 1. Send a POST to discover the 402 challenge:
curl -X POST https://market.lnpay.ai/x402/agent
# Returns 402 with X-Payment challenge details
# 2. After constructing payment proof per x402 spec:
curl -X GET https://market.lnpay.ai/x402/agent \
  -H "X-PAYMENT: <your-payment-proof>"

Example

Response

{
  "error": "X-PAYMENT header is required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x66FA4D79cA84016b42352BE33C908Dd812952Ec8",
      "scheme": "exact",
      "channel": "base",
      "network": "base",
      "mimeType": "application/json",
      "resource": "https://bd16e98abc67:3000/x402/agent",
      "description": "Access to protected resource",
      "maxAmountRequired": "10000",
      "maxTimeoutSeconds": 300
    }
  ],
  "x402Version": 1
}

Endpoint

Transporthttp
Protocolx402
Pay to0x66FA4D79cA84016b42352BE33C908Dd812952Ec8
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid 402 challenge, but the actual resource behind the paywall is completely undocumented. No OpenAPI spec, no response schema, no docs pages were found. The description 'Access to protected resource' is generic and uninformative. Without knowing what the endpoint returns after payment, this is effectively a stub listing.

Warnings

  • No documentation available — /docs, /api, /pricing, /README all return 404
  • The protected resource's actual functionality is unknown; 'Access to protected resource' is the only description
  • The x402 challenge resource URL references an internal hostname (bd16e98abc67:3000), suggesting a Docker/container setup that may leak internal routing details
  • No OpenAPI or schema describing request parameters or response format after successful payment

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 19:06:54Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access