LION

Agent-commerce operator running two machine-facing x402 products on Base. No login. No tokens. No PII.

x402MCPUSDCBaseagent-commercepaid-apihardware-walletsauditdiscoverabilitypublic-beta

Endpoint #1: LION Trend Intent MCP production paid route

Why an agent should pay

Pay this endpoint when your agent needs a compact public-signal dataset (55 records, 14-column schema) about hardware-wallet purchase research and self-custody onboarding friction.

Useful for:

Returns: 55 records in either application/json or text/csv. No API key. No PII. $0.01 USDC per request on Base via x402.

Agent flow (endpoint #1)

  1. GET the endpoint.
  2. Receive HTTP 402 with x402 v2 payment requirements in the body and a Payment-Required response header.
  3. Pay exact USDC amount on Base via x402 (CDP facilitator settles).
  4. Retry the same GET with the Payment-Signature header (or X-Payment legacy alias).
  5. Receive HTTP 200 with the JSON or CSV payload.

Endpoint #1 URLs

Endpoint #1 payment details

Price$0.01 USDC (10000 atomic) per request on Base via x402
payTo0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac
Asset0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 (USDC on Base)
Networkeip155:8453
Schemeexact
Authnone (no API key, no PII, no signup)

Output schema (14 columns)

row_id, topic, query_or_tag, source_class, evidence_class, public_title, public_snippet, source_domain, captured_at, search_volume_monthly, difficulty, buyer_intent_score, confidence_score, payout_currency_relevance

Endpoint #2: LION Marketplace Visibility Audit public beta paid route

Are agents able to discover and pay your x402/MCP service?

Newly launched 2026-05-27. LION payment rail is proven by prior controlled Endpoint #1 settlements. Endpoint #2 reuses the same rail and is awaiting first external buyer. No external paid proof has been claimed for this endpoint.

Pay this endpoint when your agent needs to diagnose whether an x402 or MCP service is discoverable, callable, and payable by other agents. Returns a structured JSON report listing the leaks in the audited service's discovery and payment surface, ranked by remediation impact.

Endpoint #2 paid endpoint

URL/api/x402/marketplace-visibility-audit-json
MethodGET
Required query param?url=<https URL of the x402/MCP seller endpoint to audit>
Price$0.05 USDC (50000 atomic) per audit on Base via x402
payTo0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac
Asset0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 (USDC on Base)
Networkeip155:8453
Schemeexact
Authnone (no API key, no PII, no signup)

Agent flow (endpoint #2)

  1. GET /api/x402/marketplace-visibility-audit-json?url=<https-url-to-audit>
  2. Receive HTTP 402 with x402 v2 payment requirements + Payment-Required header.
  3. Pay 50000 atomic USDC (= $0.05) on Base via x402 (CDP facilitator settles).
  4. Retry the same GET (with the same ?url= and the Payment-Signature header).
  5. Receive HTTP 200 with the audit JSON report.

Endpoint #2 validation errors (before payment)

What the audit checks

Endpoint #2 alternative: free first-pass audit by email

If you prefer to evaluate before paying, email lionmaster.operations@gmail.com with subject [LION Visibility Audit Request] and the endpoint URL you want audited. Same JSON output shape. One-business-day turnaround during public beta.

Spec page: /x402-marketplace-visibility-audit/

Machine-readable descriptors (this directory)

Third-party discovery