About ByteTrend

API & MCP access

Everything on this site — every score, metric and price — is served by the ByteTree API. The same data is available to your own code, spreadsheets and AI assistants.

Two ways in

The REST API returns clean JSON for assets, the four ByteTrend scores, the full metrics blob, price history, sparklines and group aggregates — everything the tables and charts on this site are built from.

The MCP server exposes the same dataset to AI assistants via the Model Context Protocol. Connect Claude (or any MCP client) and it can rank assets, compare Local against CAPR scores, pull metric series and reason about trend regimes — with ByteTree's definitions supplied in-band so the assistant grounds its answers in the same vocabulary as the definitions page.

Documentation

The full developer documentation lives at bytetree.io. Start here:

Getting started

Your first REST request in five minutes — endpoints, envelopes and examples.

Authentication

How API keys work: bearer tokens, universe scopes and capabilities.

MCP quickstart

Connect Claude or any MCP client to the ByteTree dataset.

MCP overview

The tools the MCP server exposes and how responses are shaped.

How access works

API access is authenticated with a personal key, sent as a bearer token. Each key carries a scope (which universes it can read) and a capability (read-only viewing, or full API and MCP access). Keys are issued with ByteTrend subscriptions.

We're rolling out API access progressively during the beta. If you'd like to build against the API or wire ByteTrend into an AI workflow, tell us on the feedback page — early integrators help us shape the surface.