Kristo Intelligence

io.github.hristovdimitri2-hubPublished by GitHub account hristovdimitri2-hubv6.2.0Updated Nov 4, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Paid DeFi intelligence MCP server on Base: returns trading signals, whale flow, arbitrage spreads and market stats, billed per call in USDC via x402.

What you can do
  • Read trading-agent signals for ETH, ONDO, KAITO and DEGEN with action, confidence, price and reasoning
  • Track large USDC whale transfers and cross-DEX arbitrage spreads on Base
  • Read aggregated market stats, daily counters and live price indicators
  • Inspect on-chain USDC payment history to the service's fee receiver
  • Check the service's Telegram bot status, uptime and message counters
When to use it
Useful when an assistant needs quick, machine-readable Base market context, directional trading calls or whale and arbitrage data without signing up for an API key. Try the free sample routes first to check the response shape before paying.
Requirements
Remote streamable HTTP endpoint; no account, API key or environment variable. Each paid call requires a USDC payment on Base (chain 8453) via the x402 flow: read the HTTP 402 challenge, pay the exact atomic amount to the listed receiver, then retry with the payment header. A funded Base wallet and an x402-capable client are needed.
Before you install
Every tool call costs real money in USDC (from about 0.003 per call), so automated or looping agents can spend without a clear cap. The 402 challenge is the only authoritative amount: sending the decimal display price as base units can overpay by a factor of a million and is still accepted. Signed payment payloads are single-use; an HTTP 425 means the payment already settled, so do not pay again. Signals are third-party trading opinions, not financial advice.

Installation

In SourceWeft

  1. Open Kristo Intelligence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.hristovdimitri2-hub%2Fkristo-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

Source: README.md at commit cfab9f0

Tools

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).

Takes no parameters.

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).

Takes no parameters.

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).

Takes no parameters.

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).

Takes no parameters.

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).

Takes no parameters.

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).

Takes no parameters.

Version history

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

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.