TradeOS Public Intelligence Kit

Build source-grounded crypto market Data Intelligence products on top of TradeOS public evidence.

TradeOS is the crypto-market vertical of a broader source-grounded Data Intelligence OS strategy. It is not a trading platform, broker, custodian, managed account service, or hosted execution system. See the TradeOS Business Thesis for the business overview.

This repo gives builders SDKs, MCP tools, a BYOK agent CLI, runnable bots, and the blueprint for the flagship TradeOS app pattern: a private self-hosted Symbol Cockpit.

TradeOS hosts the intelligence API. The cockpit is an individual private-use control plane: it runs on the self-hosted operator's own machine, server, quant workstation, or agent host. It can recommend buy, sell, trim, avoid, watch, or pass decisions from TradeOS evidence plus local rules, while keys, custody, portfolio context, approvals, and execution stay in that operator's environment.

Builders can package or extend this pattern for users to self-host. They should not operate the cockpit as a managed account service, collect customer exchange credentials, custody customer assets, or place orders for customers.

That private self-hosted model is the product advantage. Traders get an actionable agent. Builders get a product they can ship. TradeOS stays the source-grounded intelligence product layer instead of becoming a custodian, broker, or hosted order router.

Think of TradeOS as a crypto market Data Intelligence OS:

• TradeOS supplies the source-backed intelligence layer.
• Builders package that intelligence into briefings, bots, watchlists, dashboards, validation packs, proof pages, and widgets.
• Users and builder apps send structured feedback that improves intelligence quality and provenance.
• Paid TradeOS, x402, or enterprise access starts when a product needs scale, alerts, automation, premium history, private intelligence products, validation APIs, or explicit data rights.

The practical loop is simple:

Use TradeOS free.
Earn Data Intel Credits by improving intelligence quality.
Build and earn on public intelligence.
Pay when you need private intelligence products, scale, alerts, automation, or data rights.

Use the free public kit to prove a workflow. Charge for the packaging around that workflow. Submit feedback with provenance so TradeOS can improve the intelligence layer. Upgrade to paid TradeOS when the product needs production volume, alerts, automation, premium history, private intelligence products, validation APIs, x402 machine access, explicit data rights, or enterprise support.

The flywheel effect is the point: useful TradeOS evidence helps builders ship paid services; paid services create users, usage, feedback, and outcome labels; that feedback improves TradeOS intelligence; better intelligence makes builder products more valuable; successful products then need paid TradeOS depth, x402 access, and enterprise support.

Data Intelligence Services / SKU Map

TradeOS packages intelligence as product layers, not only as raw datasets:

Keep the boundary explicit in builder products. Human DTI credits do not unlock paid API scale, x402 calls, alert delivery, exports, automation, custody, execution, private context, or enterprise data rights. Those are paid, reviewed, or contract-entitled paths.

At A Glance

What This Is

TradeOS sits in the public market-intelligence layer for crypto and on-chain markets. It is one vertical, not the entire Source Intelligence Network strategy. This kit is the builder distribution surface for that Data Intelligence OS. It helps products discover, consume, package, and send feedback on current, source-backed market context inside bots, dashboards, agent workflows, research products, validation systems, and paid communities.

It is an evidence and feedback layer:

• public digest inputs, candidates, watchlists, thesis records, proof lookups, caveats, freshness, source refs, and invalidation notes;
• a public Fusion Signal Cockpit preview that shows redacted symbol-level direction, confidence, freshness, why-fired context, invalidation, and feedback intake without exposing execution fields;
• symbol-cockpit and action-agent patterns for turning evidence into good/bad/ugly verdicts, watchlist recommendations, and bot preflight checks;
• non-executable action intents that carry evidence-backed action context into local review, policy gates, paper execution, or independent executor experiments without becoming orders;
• TypeScript and Python SDKs for apps and services;
• a stdio MCP server for local agent hosts such as Claude Desktop and Cursor;
• a BYOK CLI that can ask Venice AI or another OpenAI-compatible model over TradeOS evidence;
• a market briefing bot that can post to stdout, Discord, or Telegram;
• structured feedback writes with provenance so TradeOS can learn which public intelligence was useful, early, late, thin, or confusing.

It is not a TradeOS-hosted broker, custody product, managed account service, or order router. Builders can wire the open-source kit into local bot, preflight, or execution stacks, but exchange keys, approvals, sizing rules, and custody stay with the self-hosted operator using it for their own account context. If a builder collects customer credentials, controls customer accounts, or runs execution for other people, that builder has created a separate managed trading service outside this kit's supported boundary.

Action intents are the bridge, not the executor. They are marked non_executable, require operator review, and deliberately omit venue, account, size, order type, route, calldata, transaction body, and execute URL fields.

In practical terms:

TradeOS Data Intelligence OS -> intelligence, evidence, data, feedback IDs
Symbol Cockpit -> private local recommendation and decision runtime
Local modules -> feasibility, EA/risk, execution adapters, ops dashboard

Why Builders Use It