Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Token Terminal (BYOK) icon

Token Terminal (BYOK)

Read standardized onchain financial metrics, projects, market sectors, assets and datasets for crypto protocols and blockchains from Token Terminal with your own API key

Unify Dynamics LLC

Tools12read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderToken Terminalunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which projects does Token Terminal cover?
Tools called
list_projects
Which chains does Aave run on?
Tools called
get_project
How much in fees did Aave earn each day this month?
Tools called
get_project_metrics
What are Aave's aggregated fee and revenue figures?
Tools called
get_project_metric_aggregations
Show Uniswap's quarterly financial statement for the last year
Tools called
get_project_financial_statement
What market sectors does Token Terminal define?
Tools called
list_market_sectors

About

Token Terminal (BYOK) lets an AI assistant read your own Token Terminal data through the Token Terminal API with a key you supply (Token Terminal API key (requires the API plan)). Read-only: 12 tools (list_projects, get_project, get_project_metrics, get_project_metric_aggregations, get_project_financial_statement, list_market_sectors, get_market_sector, list_metrics, get_metric_data, get_metric_aggregations, list_assets, get_asset). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.tokenterminal.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Token Terminal. Token Terminal and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Token Terminal API (api.tokenterminal.com) with a BYOK key; documentation: https://tokenterminal.com/docs/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

12 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data12 tools
  • List projectsList the projects (protocols and blockchains) available through the API with id, name, symbol, CoinGecko id and archived flag.
  • Get projectGet one project: name, symbol, chains it runs on, products and links.
  • Get project metricsGet historical metric values (for example fees, revenue, active users) for one project, optionally by chain, between two dates.
  • Get project metric aggregationsGet aggregated metric figures for one project, such as 30 day or annualized fees and revenue.
  • Get project financial statementGet a project's financial statement (income statement style sections of metrics) by week, month, quarter or year.
  • List market sectorsList market sectors (for example DEXs, lending, L1 chains) with id and name.
  • Get market sectorGet one market sector with its description and the projects in it.
  • List metricsList all metrics available through the API with id, name and description.
  • Get metric dataGet one metric across several projects over time, for example fees for aave and uniswap between two dates.
  • Get metric aggregationsGet aggregated figures (such as 30 day and annualized values) of selected metrics for several projects.
  • List assetsList tracked assets (tokens and stablecoins) with type, symbol, CoinGecko id and chains, one page at a time.
  • Get assetGet one asset with its token addresses per chain, products, and the list of metrics available for it.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-tokenterminal.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 12 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-tokenterminal.connectorbay.com/mcp
RESTPOST https://byok-tokenterminal.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-tokenterminal.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Token Terminal API key (requires the API plan) in the X-Upstream-Key header (get one at tokenterminal.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Token Terminal connector: questions and answers

What is the Token Terminal connector?

Token Terminal (BYOK) lets an AI assistant read your own Token Terminal data through the Token Terminal API with a key you supply (Token Terminal… It is a hosted MCP server with 12 tools such as List projects, Get project, Get project metrics, Get project metric aggregations, Get project financial statement, List market sectors, published by Unify Dynamics LLC. It is independent and not affiliated with Token Terminal.

How do I connect Token Terminal to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-tokenterminal.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-tokenterminal.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-tokenterminal.json.

Do I need a Token Terminal account or API key?

Yes: this is a bring-your-own-key connector. Create a Token Terminal API key (requires the API plan) at https://tokenterminal.com/account and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Token Terminal read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Token Terminal connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Turso (BYOK)

Read your Turso organizations, databases, groups, locations and usage figures with BYOK

Live · MCP + REST12 tools

Turso Admin (BYOK)

Read Turso plans and quotas, invoices, database and group settings, instance details, API token metadata and recently deleted databases or groups with your own Platform API token

Live · MCP + REST9 tools

Twilio Account Credentials (BYOK)

Read the names of the stored AWS credentials and public keys in your Twilio account and which countries messaging is allowed to, with your own credentials (read-only)

Live · MCP + REST5 tools

Twilio Bulk Exports (BYOK)

Read the Twilio Bulk Exports settings, the days that have exportable logs and the status of custom export jobs with your own credentials (no log contents)

Live · MCP + REST5 tools

Twilio Event Streams (BYOK)

Read your Twilio Event Streams sinks (type and status), subscriptions, subscribed event types and the catalog of event types and schemas with your own credentials (read-only)

Live · MCP + REST9 tools

Twilio Keys and Apps (BYOK)

Read the names and creation dates of your Twilio API keys and signing keys, plus TwiML application and Connect app settings, with your own credentials (secrets are never returned)

Live · MCP + REST9 tools

Documentation

Back to top

Token Terminal (BYOK) — connector documentation

  • MCP endpoint: https://byok-tokenterminal.connectorbay.com/mcp
  • REST API: POST https://byok-tokenterminal.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-tokenterminal.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Token Terminal Token Terminal API key (requires the API plan), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-tokenterminal.connectorbay.com/health · Tool schemas: https://byok-tokenterminal.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-tokenterminal · agent@connectorbay.com

What Token Terminal (BYOK) is for

Token Terminal (BYOK) lets an AI assistant read your own Token Terminal data through the Token Terminal API with a key you supply (Token Terminal API key (requires the API plan)). Read-only: 12 tools (list_projects, get_project, get_project_metrics, get_project_metric_aggregations, get_project_financial_statement, list_market_sectors, get_market_sector, list_metrics, get_metric_data, get_metric_aggregations, list_assets, get_asset). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.tokenterminal.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Token Terminal. Token Terminal and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which projects does Token Terminal cover?"
  • "Which chains does Aave run on?"
  • "How much in fees did Aave earn each day this month?"
  • "What are Aave's aggregated fee and revenue figures?"
  • "Show Uniswap's quarterly financial statement for the last year"
  • "What market sectors does Token Terminal define?"

What it does

  • list_projects: List the projects (protocols and blockchains) available through the API with id, name, symbol, CoinGecko id and archived flag.
  • get_project: Get one project: name, symbol, chains it runs on, products and links. Use it to see which chains and metrics exist before asking for metric history.
  • get_project_metrics: Get historical metric values (for example fees, revenue, active users) for one project, optionally by chain, between two dates.
  • get_project_metric_aggregations: Get aggregated metric figures for one project, such as 30 day or annualized fees and revenue.
  • get_project_financial_statement: Get a project's financial statement (income statement style sections of metrics) by week, month, quarter or year.
  • list_market_sectors: List market sectors (for example DEXs, lending, L1 chains) with id and name.
  • get_market_sector: Get one market sector with its description and the projects in it.
  • list_metrics: List all metrics available through the API with id, name and description.
  • get_metric_data: Get one metric across several projects over time, for example fees for aave and uniswap between two dates.
  • get_metric_aggregations: Get aggregated figures (such as 30 day and annualized values) of selected metrics for several projects.
  • list_assets: List tracked assets (tokens and stablecoins) with type, symbol, CoinGecko id and chains, one page at a time.
  • get_asset: Get one asset with its token addresses per chain, products, and the list of metrics available for it.

BYOK key

You bring your own Token Terminal Token Terminal API key (requires the API plan) (https://tokenterminal.com/account). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.tokenterminal.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Token Terminal API (api.tokenterminal.com) with a BYOK key; documentation: https://tokenterminal.com/docs/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Token Terminal. Token Terminal and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Token Terminal account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Token Terminal (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Token Terminal (BYOK) is. Token Terminal (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Token Terminal data: Read standardized onchain financial metrics, projects, market sectors, assets and datasets for crypto protocols and blockchains from Token Terminal with your own API key. You bring your own Token Terminal Token Terminal API key (requires the API plan); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Token Terminal call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.tokenterminal.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Token Terminal rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Token Terminal receives. The request we make on your behalf, including the key and the arguments, under Token Terminal's own terms and privacy policy. Token Terminal acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Token Terminal gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Token Terminal data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Token Terminal (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Token Terminal at any time to end all access.

Children. Token Terminal (BYOK) is a general-audience service operated by the adult using the assistant, under Token Terminal's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Token Terminal (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Token Terminal (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Token Terminal (BYOK) provides: Read standardized onchain financial metrics, projects, market sectors, assets and datasets for crypto protocols and blockchains from Token Terminal with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Token Terminal credentials and only access data you are allowed to access. Token Terminal's terms apply to your use of Token Terminal; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Token Terminal. Token Terminal and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Token Terminal returns, lightly trimmed; it may be incomplete, delayed or changed by Token Terminal. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Token Terminal account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Token Terminal's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Token Terminal may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Token Terminal key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Token Terminal takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-tokenterminal

Token Terminal (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Token Terminal (BYOK) never asks for them.

Get Token Terminal (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Token Terminal Token Terminal API key (requires the API plan). Create one at https://tokenterminal.com/account, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Token Terminal. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Token Terminal.