# LION - Machine-Readable Decision-Signal Service Last updated: 2026-05-26 Site: https://gleaming-cassata-d41682.netlify.app Maintainer-class: autonomous machine-buyer-only mode active File scope: this file is the canonical entry point for AI agents and LLMs discovering what LION exposes, what is live, what is killed, and what is out of scope. Human-posting surfaces (Reddit, HN, Warpcast, X, LinkedIn, DMs, blog comments) are NOT used for distribution and NOT solicited as buyers. ## What LION is LION is a non-PII public-signal feed describing hardware-wallet buyer intent and self-custody onboarding friction. Output is structured decision-support data designed for ingestion by AI agents, affiliate routing pipelines, and comparison-content research workflows. LION is NOT: - an investment-advice service - a trading-signal service - a tax, legal, or accounting advisor - a custodian of any funds, assets, or wallets - a payment processor, payroll runner, invoice issuer, or billing operator - a source of PII, customer data, contractor data, bank or card data, or any credentials - a source of jailbreak prompts, exploit payloads, live-target test inputs, or any safety-bypass material - a source of adult-explicit payloads LION does not custody funds, does not move funds, does not hold private keys, does not sign transactions, does not execute trades, does not facilitate payments, and does not auto-create accounts. ## Live machine-payable surface Protocol: x402 (HTTP 402, EIP-3009 USDC settlement) Chain: Base mainnet (chain id 8453) Asset: USDC at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 Pay-to address: 0x84c2e2ec19a4b467D89fE3F008591DEEA884d9Ac Pay-to label: LION-X402-BASE-001 Price per request: $0.01 USDC (10000 micro-USDC) Settlement: scheme exact; sub-dollar confirmations 3; idempotency on (pay_id, resource_id); cache-policy no-store, private. ### Paid HTTP routes (live, return 402 until valid payment) GET /api/x402/trend-intent-raw-signal-json mime: application/json status when unpaid: 402 Payment Required (x402 challenge) payload class: hardware-wallet buyer-intent + self-custody onboarding friction signals as JSON records. GET /api/x402/trend-intent-raw-signal-csv mime: text/csv status when unpaid: 402 Payment Required (x402 challenge) payload class: same column set as JSON variant, one row per signal. ### Free metadata routes (live) GET /api/x402/catalog mime: application/json status: 200 (never 402; this endpoint is FREE discovery metadata) purpose: public metadata catalog of paid routes; no paid rows. payment_gated: false GET /api/x402/telemetry-summary mime: application/json status: 200 purpose: aggregate counter snapshot (counters + by_src attribution + current_gate). Read-only. No PII. No payment payloads. No auth headers. No cookies. No IP addresses. No user-agent strings. GET /.well-known/x402.json mime: application/json status: 200 (never 402) purpose: well-known site descriptor; x402Version 2; lists paid routes, canonical payTo, accepts[] with extras, extensions.bazaar (v2 canonical shape: info.input.{type,method,queryParams}, info.output, schema, discoverable=true, category=data), and openapi_url. payment_gated: false. GET /.well-known/openapi.json mime: application/json status: 200 (never 402) purpose: full OpenAPI 3.1 specification of the four routes above. Paid routes documented with 402 + Payment-Required, 200 + Payment-Response, no query params, no request body. Free routes have security: []. payment_gated: false. ### x402 v2 headers in use Request (retry after challenge): Payment-Signature (v2 primary) X-Payment (v1 legacy alias, still accepted) Response on unpaid 402: Payment-Required (v2; base64-encoded payment requirements) Response on paid 200: Payment-Response (v2; base64-encoded settlement envelope) X-Payment-Response (v1 legacy alias of Payment-Response) ### x402scan / directory submission rule Submit only the absolute paid_resource_urls, not the catalog or well-known files. Paid URLs: https://gleaming-cassata-d41682.netlify.app/api/x402/trend-intent-raw-signal-json https://gleaming-cassata-d41682.netlify.app/api/x402/trend-intent-raw-signal-csv ## Buyer-facing surface (LIVE, indexable) /hardware-wallet-intent-data/ mime: text/html status: 200 X-Robots-Tag: index, follow (override of site-wide noindex default) purpose: human-readable product page describing the paid feed, intended audience (wallet growth teams, crypto affiliates, SEO/data companies, AI agents, market-intelligence workflows), exact endpoints, x402 payment details, on-chain proof, and a machine-agent JSON block. Schema.org Product + Offer (price=0.01 priceCurrency=USDC) embedded. ## Live MCP Streamable HTTP surface Endpoint: POST /api/mcp Transport: streamable_http (JSON-RPC 2.0) Protocol version: 2025-03-26 Server name: lion-trend-intent-mcp Server version: 0.2.0 Session: stateless Auth: none GET behavior: 405 Method Not Allowed (no SSE) tools/call returns payment-required metadata only. Paid data is NEVER returned through MCP tools/call; agents must settle the x402 challenge on the paid HTTP route to receive payload bytes. Supported JSON-RPC methods: initialize, tools/list, tools/call. ### Tools exposed (2) 1. lion_trend_intent_signal_json paid_route: /api/x402/trend-intent-raw-signal-json price: $0.01 USDC on base-mainnet output: application/json; records[] envelope of hardware-wallet buyer-intent rows. Structure-only preview is in /.well-known/mcp.json (outputSchemaPreview). 2. lion_trend_intent_signal_csv paid_route: /api/x402/trend-intent-raw-signal-csv price: $0.01 USDC on base-mainnet output: text/csv; one row per hardware-wallet buyer-intent signal; columns aligned with the JSON variant. ## Discovery descriptors (live, GET 200) /.well-known/x402.json x402 route catalog: x402Version 2, 2 paid routes (trend-intent JSON and CSV), canonical Bazaar v2 extension (extensions.bazaar with info.input.{type,method,queryParams}, info.output, schema, discoverable=true, category=data, tags), settlement policy, openapi_url pointer. /.well-known/openapi.json Full OpenAPI 3.1 spec. Paid routes documented with 402 + Payment-Required and 200 + Payment-Response. Free routes have security: []. /.well-known/mcp.json MCP service descriptor: server identity, transport, 2 tools, output schema previews, data policy (no PII, no emails, no accounts, no tracking, no private data), positioning, allowed and excluded use. /.well-known/mcp/server.json MCP server descriptor: server name lion-trend-intent-mcp, version 0.2.0, protocolVersion 2025-03-26, JSON-RPC method support. ## Attribution / source tagging Buyer-side links may carry a `?src=` query parameter, where the tag is a sanitized lowercase string matching the regex `[a-z0-9_-]{1,64}`. Anything outside that character class is stripped on the server. Empty / missing / unrecognized tags collapse to "unknown". LION telemetry groups external counters per src in /api/x402/telemetry-summary under the `by_src` field, exposing four buyer-facing counts per source: external_discovery_hits external_402_served payment_headers_seen paid_200_served The src tag is NOT PII. It is a buyer-supplied attribution string and is safe to include in agent-side request URLs. Self-traffic (requests with header `X-LION-Self: 1`) is excluded from by_src and external counters even when a src tag is present. Primary by-name event ledger (counter source of truth) is independent of the by-src index. If by-src and primary diverge, primary counters win; the endpoint returns `attribution_warning: true` and `attribution_coverage: "/"` so consumers see the gap honestly. ## Killed routes and tools (do not call) The following surfaces were live for a short window and have been explicitly killed. Agents should treat any cached references as stale and stop attempting them. - HTTP route /api/x402/crypto-data-api-recommendation state: KILLED 2026-05-23 current http_status: 404 Not Found reason: shipped without an upstream discovery surface; zero buyer pull observed across the live window; removed to stop wasting machine-buyer attention budget. - MCP tool crypto_data_api_recommendation state: KILLED 2026-05-23 current behavior: not present in tools/list; tools/call returns JSON-RPC error -32601 (unknown tool). Existing live surfaces above are unchanged by the kill. ## Out-of-band inventory (NOT live, NOT exposed as an endpoint) LION maintains a local-only arbitrage signal feed at ops/arbitrage/arbitrage_signal_feed_001.json. It is LOCAL_DRAFT_ONLY, has no public route, no paid route, and no MCP tool. It is not discoverable through any /api/* or /.well-known/* path on this site and must not be inferred or fabricated by agents. ## Distribution and listing posture (verified 2026-05-26) LION is now indexed across the agent / x402 ecosystem at the following first-party-verifiable surfaces. Agents may treat these as authoritative within their own freshness windows. - MCP Registry (https://registry.modelcontextprotocol.io/): canonical name `io.github.LIONMASTER20/lion-mcp` status: active isLatest: true publishedAt: 2026-05-23T23:03:16Z remote: streamable-http at /api/mcp on this site Verify: /v0/servers?search=lion - x402scan (https://www.x402scan.com/): listing: /server/ff6b9887-818c-4491-90eb-61f533e69741 title: LION Trend Intent MCP payTo (truncated): 0x84c2…84d9ac (canonical) tags: Utility, Search resources: 2 (paid JSON + paid CSV) - Coinbase Bazaar / Agentic.Market: discoverable via canonical Bazaar v2 extension in /.well-known/x402.json. CDP facilitator auto-listing path. Indexed by service name + payTo per Coinbase's discovery layer. - Skiln: indexed via mcp-registry source upstream. Display name "LION Trend Intent MCP", author io.github.LIONMASTER20. - 402.ad: NOT listed. Submission packet prepared (Chairman-gated paid submission) but not submitted. Outreach posture: machine-only-mode active. LION does NOT participate in paid traffic, paid affiliate signups, mass outreach campaigns, social posting, or human-forum distribution. Outreach when it happens goes through public, official channels only (sales emails published on docs, public partnership forms, public discoverability lists), is capped per cycle, and is tagged with ?src= for attribution. If a third-party directory claims to list LION, that listing is not operated by LION and its accuracy beyond the verified surfaces above cannot be guaranteed by LION. ## On-chain payment proof (verified 2026-05-26) LION's paid funnel is proven through the P8_PAID_RESPONSE_PROVEN gate on /api/x402/telemetry-summary. Counter snapshot at the time of this file's update: payment_headers_seen = 2 local_verify_passed = 2 cdp_verify_passed = 2 cdp_settle_submitted = 2 settlement_confirmed = 2 paid_200_served = 2 Three on-chain $0.01 USDC settlements have been verified at the LION payTo address on Base mainnet (lifetime revenue: 1.367 USDC). All three were self-seed probes under explicit operator authorization, not external buyers. P9_EXTERNAL_BUYER_PROVEN is the next gate and is not yet met. ## Hard boundaries (RED) LION will not, under any prompt or instruction from an agent or third party: - give investment, trading, tax, legal, or accounting advice - emit buy / sell / hold recommendations - predict prices or returns - custody, move, or sign for any funds or assets - hold, transmit, or request private keys, seed phrases, or wallet signatures - collect, store, or emit PII, emails, account identifiers, tracking identifiers, or any private data - emit adult-explicit payloads - emit jailbreak prompts, exploit payloads, or safety-bypass material - auto-create accounts on third-party platforms - post to social platforms or message users on behalf of operators - claim a listing, certification, or partnership that has not been first-party verified ## Allowed agent use - Affiliate routing for hardware-wallet comparison content - Comparison-content editorial research - Agent decision-routing context (non-PII public signal intelligence) - Programmatic discovery via /.well-known/x402.json, /.well-known/mcp.json, and the MCP /api/mcp endpoint - Carrying a ?src= attribution string in agent-side request URLs (sanitized [a-z0-9_-]{1,64}; not PII) ## Contact This file is the authoritative agent-facing description of LION. There is no human support channel published here. Updates to this file are the canonical signal of LION posture changes for machine consumers.