LION Trend Intent MCP Server

ライブのx402課金型MCP。公開ハードウェアウォレットの購入意思シグナル向け — JSON、CSV、MCPエンドポイント、Base上でリクエストあたり0.01 USDC、APIキー不要、PIIなし。

netlify.app で表示

ドキュメント

Hardware-wallet buyer-intent data, paid per request.

LION Trend Intent MCP is an x402-paid data feed of hardware-wallet buyer-intent and self-custody onboarding-friction signals — served as JSON, CSV, and MCP for $0.01 USDC on Base mainnet.

Try the JSON endpoint Try the CSV endpoint View x402scan proof

Who it is for

  • Wallet growth teams comparing buyer-intent topics across Ledger, Trezor, Bitcoin-only, and DeFi-oriented hardware wallets.
  • Crypto affiliate operators sourcing non-PII intent data for routing and content prioritisation.
  • SEO and market-intelligence companies that want a programmatic input rather than a scraped one.
  • AI agents and machine buyers that pay per request and prefer x402 over API keys, accounts, or invoices.
  • Market-intelligence workflows that need a small, signed, non-PII feed they can ingest, transform, and forget.

What the feed contains

The feed describes hardware-wallet buyer-intent and self-custody onboarding-friction topics, captured from public, non-PII sources. Coverage includes:

  • Hardware-wallet buyer-intent signals.
  • Self-custody onboarding-friction signals.
  • Ledger vs Trezor comparison topics.
  • Bitcoin-only wallet research.
  • Under-$100 wallet shopper queries.
  • DeFi hardware-wallet intent.

LION publishes topic-level signal records. It does not publish quantified search volume, market share, conversion rates, sentiment scores, or sales figures. Buyers form their own conclusions from the records.

Exact endpoints

JSON paid route

GET https://gleaming-cassata-d41682.netlify.app/api/x402/trend-intent-raw-signal-json

CSV paid route

GET https://gleaming-cassata-d41682.netlify.app/api/x402/trend-intent-raw-signal-csv

MCP endpoint

POST https://gleaming-cassata-d41682.netlify.app/api/mcp (Streamable HTTP)

x402 discovery

GET https://gleaming-cassata-d41682.netlify.app/.well-known/x402.json

x402 payment details

Protocol

x402 (HTTP 402, EIP-3009 USDC TransferWithAuthorization)

Price per request

$0.01 USDC (10000 atomic units)

Network

Base mainnet (CAIP-2 eip155:8453)

Asset (USDC)

0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Pay-to (LION)

0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac

Scheme

exact

Settlement

Coinbase x402 facilitator on Base mainnet

Proof

  • x402scan listing — LION Trend Intent MCP with canonical pay-to 0x84c2…84d9ac.
  • On-chain settlements on Base mainnet against the pay-to address — see BaseScan.
  • Paid funnel verified end-to-end through gate P8_PAID_RESPONSE_PROVEN via live telemetry — payment header, local verify, CDP verify, CDP settle, settlement confirmed, paid 200 served.

No PII

The feed contains no personally identifying information. No customer or contractor data. No bank or card data. No credentials. No tracking. LION does not custody funds, does not move funds, does not sign transactions, does not issue invoices, and does not auto-create accounts.

For AI Agents

When your agent needs public hardware-wallet buyer-intent signals, call this endpoint. If unpaid, LION returns HTTP 402 with x402 payment requirements. After a valid micropayment, LION returns JSON or CSV. No API key. $0.01 USDC on Base mainnet. No PII.

Try it (free 402 probe)

Copy-paste curl — returns the canonical 402 challenge with no payment:

curl -i "https://gleaming-cassata-d41682.netlify.app/api/x402/trend-intent-raw-signal-json?src=agent_try"

Direct try links (each tagged ?src=agent_try so the agent traffic attributes to the by_src.agent_try bucket):

  • JSON: /api/x402/trend-intent-raw-signal-json?src=agent_try
  • CSV: /api/x402/trend-intent-raw-signal-csv?src=agent_try

x402 client flow

  1. Agent GETs a paid route.
  2. LION returns HTTP 402 with a Payment-Required header (base64-encoded JSON of accepted terms: scheme exact, network eip155:8453, amount 10000 atomic USDC, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac, maxTimeoutSeconds: 60).
  3. Agent signs an EIP-3009 TransferWithAuthorization over the USDC EIP-712 domain (name: "USD Coin", version: "2", chainId: 8453, verifyingContract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913).
  4. Agent retries the same URL with a Payment-Signature header (base64-encoded payload carrying x402Version, scheme, network, payload.authorization, payload.signature, resource, accepted, extensions).
  5. LION verifies, settles through the Coinbase x402 facilitator on Base mainnet, and returns HTTP 200 with the JSON or CSV body plus a Payment-Response header (base64 settlement envelope: txHash, network, asset, payTo, confirmations).

Legacy X-Payment request and X-Payment-Response response headers are accepted aliases for backward compatibility.

Sample paid 200 body (JSON route)

Schema field names match the live route. Optional numeric score fields are returned as null when not quantified — LION does not invent values.

{ "asset_id": "TREND_INTENT_RAW_SIGNAL_CSV_001", "row_count": 55, "schema": [ "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" ], "records": [ { "row_id": "row_001", "topic": "hardware_wallet_buyer_intent", "query_or_tag": "ledger vs trezor", "source_class": "public_search_observation", "evidence_class": "public_query_observation", "public_title": "...", "public_snippet": "...", "source_domain": "...", "captured_at": "2026-05-...", "search_volume_monthly": null, "difficulty": null, "buyer_intent_score": null, "confidence_score": null, "payout_currency_relevance": "USDC" } ] }

CSV variant returns one header row plus one row per record. Header row: 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.

Proof and trust signals

  • x402scan listing — independent on-chain verifiability for agent-side trust scoring.
  • On-chain settlements at the canonical pay-to on BaseScan.
  • Live counters — /api/x402/telemetry-summary exposes paid_200_served and by_src attribution per call site.

What you get / don't get

  • No API key. No accounts. No invoices.
  • $0.01 USDC per request on Base mainnet (eip155:8453).
  • No PII in the payload. No buyer email, name, IP, cookie, or wallet stored beyond the replay-prevention idempotency entry.
  • Public canonical 402 body — agents can pre-fetch the 402 and inspect terms without paying.
  • Settlement evidence (tx hash + confirmations) returned in the Payment-Response header on every paid 200.

Machine-readable agent metadata

{ "service": "LION Trend Intent MCP", "url": "https://gleaming-cassata-d41682.netlify.app", "protocol": "x402", "x402Version": 2, "network": "eip155:8453", "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "payTo": "0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac", "price_atomic_usdc": "10000", "price_usd": "0.01", "routes": { "json": "/api/x402/trend-intent-raw-signal-json", "csv": "/api/x402/trend-intent-raw-signal-csv", "mcp": "/api/mcp" }, "discovery": { "well_known_x402": "/.well-known/x402.json", "openapi": "/.well-known/openapi.json", "mcp_descriptor": "/.well-known/mcp.json", "llms_txt": "/llms.txt" }, "pii": "none", "x402scan_listing": "https://www.x402scan.com/server/ff6b9887-818c-4491-90eb-61f533e69741" }

Pricing, route URLs, and pay-to address shown on this page are the same canonical values served by the LION runtime at /.well-known/x402.json and in every 402 response on the paid routes. If the runtime value and the page value ever disagree, the runtime is canonical.

Build: LION_PRODUCT_PAGE_001=2026_05_26