Kristo Intelligence

io.github.hristovdimitri2-hub由 GitHub 账号 hristovdimitri2-hub 发布v6.2.0更新于 Nov 4, 2026

Pay-per-call DeFi intelligence for AI agents on Base — x402, USDC, no keys.

已验证Streamable HTTP可网页运行金融数据与分析

概览

AI 生成的概览

Base 上的付费 DeFi 情报 MCP 服务器:返回交易信号、巨鲸资金流、套利价差与市场统计,按次以 USDC 通过 x402 计费。

可以做什么
  • 读取 ETH、ONDO、KAITO 和 DEGEN 的交易代理信号,含操作方向、置信度、价格与理由
  • 追踪 Base 上的大额 USDC 巨鲸转账与跨 DEX 套利价差
  • 读取聚合市场统计、每日计数与实时价格指标
  • 查看支付给该服务收款地址的链上 USDC 付款记录
  • 检查该服务的 Telegram 机器人状态、运行时长与消息计数
适用场景
适合需要快速获取机器可读的 Base 市场背景、方向性交易判断或巨鲸与套利数据,且不想注册 API 密钥的场景。建议先用免费样例接口确认返回结构,再决定是否付费。
运行要求
远程 streamable HTTP 端点;无需账号、API 密钥或环境变量。每次付费调用需在 Base(链 8453)上以 USDC 付款,走 x402 流程:读取 HTTP 402 挑战,向指定收款地址支付准确的原子金额,再带付款头重试。需要已充值的 Base 钱包和支持 x402 的客户端。
安装前请注意
每次工具调用都花费真实 USDC(约每次 0.003 起),自动化或循环调用的代理可能在无上限的情况下持续花钱。402 挑战是唯一权威金额:把小数显示价格当作原子单位发送可能多付一百万倍且仍会被接受。签名付款载荷仅可使用一次;返回 HTTP 425 表示付款已上链结算,不要重复付款。信号属第三方交易观点,不构成投资建议。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Kristo Intelligence,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.hristovdimitri2-hub%2Fkristo-intelligence/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "kristo-intelligence": {
      "type": "http",
      "url": "https://kristo-intelligence-api.onrender.com/mcp"
    }
  }
}

README

Kristo Intelligence — DeFi Signals API on Base

[Kristo Intelligence MCP connector — Glama score] [Kristo Intelligence MCP server — Glama score] [License: MIT] [Kristo Intelligence MCP server]

Paid DeFi market intelligence for AI agents. x402-native: agents pay per call in USDC, from $0.003 — no signup, no API keys, no subscriptions.

Live API: https://kristo-intelligence-api.onrender.com Marketplace listing (settlement-verified): https://payapi.market/api/kristo-intelligence-defi-signals-api

What it is

Kristo Intelligence is a live trading-agent API on the Base network (Coinbase's L2). Every call returns machine-readable market intelligence:

  • Trading-agent signals — for ETH, ONDO, KAITO and DEGEN: action, 0–1 confidence score, current USD price, and one-line reasoning
  • Whale flow — large USDC transfer tracking on Base (transfers ≥ $5M, labeled counterparties)
  • Arbitrage radar — cross-DEX spreads, refreshed every 60 seconds
  • Rug-risk checks — pre-trade safety screening
  • Market stats — aggregated activity (CoinGecko, DEXScreener, Fear & Greed)

Payment (x402)

The API speaks the x402 payment standard. The flow is three steps and works from any HTTP client:

  1. GET any paid endpoint → HTTP 402 with a self-describing challenge (exact USDC amount, receiver address, chain)
  2. Send that USDC amount on Base to the listed receiver
  3. Retry the call with the payment header → 200 with your data

No keys. No accounts. Settled in USDC on Base (chain 8453). Prices start at $0.003 per call — the complete list is below.

Two payment rails

Prefer rail 1: it is what the x402 ecosystem (x402-fetch, x402scan, facilitators) speaks.

  • Rail 1 — standard x402. The 402 carries the canonical PAYMENT-REQUIRED header (base64) and a body whose accepts[0] states the exact atomic amount, payTo, asset and CAIP-2 network for that route. Sign an EIP-3009 transferWithAuthorization for that amount (scheme exact) and retry the same request with the payload base64url-encoded in the PAYMENT-SIGNATURE header. Settlement runs through the facilitator automatically. Clients still on x402 v1 send the same payload in X-PAYMENT; both are accepted, and PAYMENT-SIGNATURE wins when both are present.
  • Rail 2 — manual fallback. Send the atomic amount yourself: take accepts[0].amount from the 402 body verbatim — "5000" means 0.005 USDC — transfer that many base units of USDC on Base (chain 8453), wait for 12 confirmations (~24s), then retry with X-Payment-Proof: base64url(JSON({payer, transaction_hash, amount_usdc})), whose amount_usdc is the same atomic value. If your wallet API wants a decimal amount, divide by 1e6 first. Do not send the decimal display price as if it were base units: the on-chain check is amount >= price, so a 1,000,000× overpayment is accepted rather than rejected. The 402 is the only authoritative amount, and the kristo-x402-client does this conversion for you.

A signed payload is single-use. HTTP 425 means your payment already settled on-chain but our node has not reached the confirming block yet — retry the same request shortly and do not pay again. HTTP 401 means a credential was presented but is unusable (bad signature, wrong amount or receiver, expired authorization window, or an already-used transaction).

Prices

These six routes are the complete paid surface. The table is checked against the live price map by tests/test_visibility_seo.py, so the README cannot drift away from the amounts the 402 challenges actually demand:

RouteUSDC per call
GET /api/v1/signal0.003
GET /api/v1/whaleflow0.003
GET /api/stats0.005
GET /api/sales0.005
GET /api/bot-status0.005
GET /api/arb/opportunities0.005

Every one of them has a free /sample twin returning the real response shape with example data — see the discovery list below. Try the shape before spending anything.

[x402 Trust: grade B, recommendation proceed]

MCP (Model Context Protocol)

The API is exposed as an MCP server for Claude Desktop, Cursor, Continue, LangChain and any MCP-compatible client:

  • SSE transport: https://kristo-intelligence-api.onrender.com/mcp/sse
  • Streamable HTTP transport: POST https://kristo-intelligence-api.onrender.com/mcp (JSON-RPC 2.0 — initialize, tools/list, tools/call, ping)

MCP tools:

ToolWhat it returnsPrice (USDC/call)
get_market_statsMarket activity, daily stats, live market data0.005
get_onchain_salesReal on-chain sales history (USDC transfers)0.005
get_bot_statusTelegram bot integration status0.005

Each tool advertises its x402 price inline, so an agent can decide and pay without reading docs.

Discover via PayAPI

The listing lives on PayAPI Market and can be discovered through PayAPI's own MCP server — agents already connected to the marketplace warehouse will find our routes from both sides:

json
{  "mcpServers": {    "payapi": {      "url": "https://payapi.market/mcp"    }  }}

Listing: https://payapi.market/api/kristo-intelligence-defi-signals-api

Try it — one command

The public reference client walks the full payment path (discovery → 402 challenge → paid retry) with no wallet required in demo mode:

bash
python examples/demo_agent/demo_agent.py --endpoint /api/v1/signal

Free discovery surfaces (no payment needed):

  • x402 discovery: /.well-known/x402
  • OpenAPI 3.0: /openapi.json
  • MCP manifest: /api/mcp/manifest
  • Agent manifest: /agents.json
  • LLM-friendly API description: /llms.txt
  • Quickstart snippets (curl/Python/Node): /api/v1/quickstart
  • Checkable facts (status, uptime, on-chain history): /validation
  • Health: /health

A free sample of every paid route — real response shape, example data, no payment and no signup. Use these to build and test a client before spending anything:

Free sampleMirrors
GET /api/v1/signal/sample/api/v1/signal
GET /api/v1/whaleflow/sample/api/v1/whaleflow
GET /api/stats/sample/api/stats
GET /api/sales/sample/api/sales
GET /api/bot-status/sample/api/bot-status
GET /api/arb/opportunities/sample/api/arb/opportunities

Repository layout

main.py                  # Flask app: API, x402 paywall, agents, transportsapp/blueprints/discovery.py  # Discovery surfaces (.well-known, MCP, llms.txt)services/                # CoinGecko client, DeFi signals, trading agentblockchain/wallet.py     # Base wallet, USDC transfers, on-chain verificationscripts/                 # On-chain recon tools, demo agent, E2E helpersexamples/demo_agent/     # Public reference x402 clientdocs/                    # Audit reports, recon findings, outreach docstests/                   # Test suite (655 tests)

Verification

  • Settlement-verified on PayAPI Market: 4 independent paid canaries settled on-chain, zero payment incidents
  • x402 registered: 11 resources on x402scan, canonical v2 challenges (CAIP-2 eip155:8453, atomic units, bazaar schema)
  • 23/23 adversarial audit (mystery-agent simulation, 2026-08-29 — a dated snapshot; see the banner in docs/MYSTERY_AGENT_REPORT.md)
  • 655 automated tests in this repository

Docs

  • docs/MARKET_WRITEUP.md — on-chain audit of the machine-payments market
  • docs/PAYER_ORIGIN.md — who actually pays on this market
  • docs/MYSTERY_AGENT_REPORT.md — adversarial buyer simulation (2026-08-29; its two price figures and its "standard rail not honoured" note are superseded — the file opens with a banner saying exactly what changed)
  • docs/RECON_FINDINGS.md — ongoing on-chain recon notes

License

MIT — the full standard text is in LICENSE.

The payment receiver and endpoint structure are stable invariants — discovery surfaces and integrations depend on them.

Commercial use notice

This software executes real financial transactions on the Base blockchain network when AGENT_AUTO_EXECUTE=true. The authors and copyright holders assume no responsibility for financial losses resulting from the use of this software. Always test on Base Sepolia testnet before mainnet deployment.

来源:README.md,提交 cfab9f0

工具

6

get_market_stats

Read-only operation — no side effects, no parameters. Returns the live Base market snapshot: aggregated activity, daily request/sales counters, the official agent catalog, and real-time market data (CoinGecko, DEXScreener, Fear & Greed). Use it for market context and price/indicator lookups; use get_onchain_sales for paid-call revenue and get_bot_status for integration health. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).

无需输入参数。

get_onchain_sales

Read-only operation — no side effects, no parameters. Returns the real on-chain payment history to this service's fee receiver on Base: total_volume_usd, total_sales, by_token, up to 100 history rows (tx hash, payer, amount, block, timestamp), source="real_blockchain", plus the wallet state and a market snapshot. Use it when you need provable revenue or settlement evidence; use get_market_stats for prices and get_bot_status for integration health. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).

无需输入参数。

get_bot_status

Read-only operation — no side effects, no parameters. Returns the service's Telegram integration status as JSON: telegram_bot_running, telegram_token_configured, last_heartbeat, uptime_started, messages_sent, active_users, commands_processed, vip_invites_sent, plus the wallet state. Use it to confirm this service's own monitoring is alive (and its heartbeat recent) before trusting other outputs; use get_market_stats for market data or get_onchain_sales for provable revenue. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).

无需输入参数。

get_trading_signal

Read-only operation — no side effects, no parameters. Returns this service's flagship trading-agent signals for ETH, ONDO, KAITO and DEGEN: action, confidence, price_usd and the model's reasoning. Use it when you need a directional call rather than raw market data; use get_whale_flow for large-transfer flow and get_arbitrage_opportunities for cross-DEX spreads. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).

无需输入参数。

get_whale_flow

Read-only operation — no side effects, no parameters. Returns network-wide USDC whale flow on Base: transfers of $5M or more, refreshed every 60 seconds, with labelled counterparties. Use it to see where size is moving; use get_trading_signal for directional calls or get_market_stats for broad context. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).

无需输入参数。

get_arbitrage_opportunities

Read-only operation — no side effects, no parameters. Returns live cross-DEX arbitrage spreads on Base, refreshed every 60 seconds. Use it for executable price gaps between venues; use get_market_stats for aggregate prices or get_trading_signal for directional calls. Paid via x402 (HTTP 402 challenge with the exact USDC amount and receiver on Base).

无需输入参数。

版本历史

4
  1. v6.2.0最新Nov 4, 2026
  2. v6.1.0Nov 3, 2026
  3. v6.0.0Sep 17, 2026
  4. v5.0.0Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。