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

Enso (BYOK)

Browse Enso's DeFi reference data (supported networks, protocols, DeFi and base tokens with APY and TVL, token prices, bundle standards and LayerZero pools) with your own API key

Unify Dynamics LLC

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

Try asking

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

Which chains does Enso support?
Tools called
list_networks
Which DeFi projects does Enso support?
Tools called
list_projects
Which protocols does Enso support for the aave project?
Tools called
list_project_protocols
Which DeFi protocols can Enso route into on Base?
Tools called
list_protocols
Which Aave V3 tokens on Ethereum have the highest TVL according to Enso?
Tools called
list_tokens
What is the price of WETH on Ethereum according to Enso?
Tools called
get_token_price

About

Enso (BYOK) lets an AI assistant read your own Enso data through the Enso API with a key you supply (Enso API key). Read-only: 9 tools (list_networks, list_projects, list_project_protocols, list_protocols, list_tokens, get_token_price, list_aggregators, get_protocol_standard, get_layerzero_pool). 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.enso.build. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Enso. Enso and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Enso API (api.enso.build) with a BYOK key; documentation: https://docs.enso.build/pages/api-reference/overview. 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

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

OpenAPI
Read your data9 tools
  • List networksList the blockchain networks Enso supports with chain id and name, optionally filtered by name or chain id.
  • List projectsList the DeFi projects (for example aave, uniswap, morpho) Enso integrates with, with the chains and protocol slugs of each.
  • List project protocolsList the protocols (versions and forks) that belong to one DeFi project, with description, link and supported chains.
  • List protocolsList every protocol Enso supports with its project, name, description and the chains it is available on, optionally for one chain or slug.
  • List tokensList base and DeFi tokens Enso knows about (vault, lending and LP tokens included) with APY, reward APY and TVL, filterable by chain, project,…
  • Get token priceGet Enso's USD price for one token on one chain, with decimals, symbol, timestamp and a confidence score.
  • List aggregatorsList the swap aggregators Enso can route through, optionally for one chain.
  • Get protocol standardGet the actions (deposit, redeem, borrow, swap and so on), function names, inputs and supported chains Enso offers for one protocol slug, plus its…
  • Get layerzero poolLook up the LayerZero Stargate pool address for a token on a chain, optionally with the pool on a destination chain.

Information

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

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-enso.connectorbay.com/mcp
RESTPOST https://byok-enso.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-enso.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 Enso API key in the X-Upstream-Key header (get one at developers.enso.build).
  • Ask a question; the agent picks the right tool and answers from the live data.

Enso connector: questions and answers

What is the Enso connector?

Enso (BYOK) lets an AI assistant read your own Enso data through the Enso API with a key you supply (Enso API key). It is a hosted MCP server with 9 tools such as List networks, List projects, List project protocols, List protocols, List tokens, Get token price, published by Unify Dynamics LLC. It is independent and not affiliated with Enso.

How do I connect Enso to Claude, ChatGPT or Cursor?

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

Do I need a Enso account or API key?

Yes: this is a bring-your-own-key connector. Create a Enso API key at https://developers.enso.build 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 Enso read-only?

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

Is the Enso 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

Realtime Register (BYOK)

Read your Realtime Register domain portfolio, DNS zones, credit balance, transactions and TLD rules with your own API key

Live · MCP + REST11 tools

Rebilly (BYOK)

Read your Rebilly billing customers, subscriptions, invoices, transactions, plans, products and coupons with your own secret API key

Live · MCP + REST9 tools

Rebilly (BYOK)

Read the setup of your Rebilly account (shipping rates, payment method and gateway catalogs, fees, webhooks, websites, gateway accounts, journal accounts and risk rules) with your own secret API key

Live · MCP + REST9 tools

Recharge (BYOK)

Read your Recharge subscriptions, charges, orders, plans, products and discounts with your own API access token

Live · MCP + REST10 tools

Recurly (BYOK)

Read your Recurly accounts, subscriptions, invoices, transactions and plans with BYOK (US data center, API v2021-02-25)

Live · MCP + REST8 tools

Recurly Catalog (BYOK)

Read your Recurly plan details, plan add-ons, items, coupons, measured units, shipping methods and price segments with your own private API key

Live · MCP + REST9 tools

Documentation

Back to top

Enso (BYOK) — connector documentation

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

What Enso (BYOK) is for

Enso (BYOK) lets an AI assistant read your own Enso data through the Enso API with a key you supply (Enso API key). Read-only: 9 tools (list_networks, list_projects, list_project_protocols, list_protocols, list_tokens, get_token_price, list_aggregators, get_protocol_standard, get_layerzero_pool). 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.enso.build. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Enso. Enso 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 chains does Enso support?"
  • "Which DeFi projects does Enso support?"
  • "Which protocols does Enso support for the aave project?"
  • "Which DeFi protocols can Enso route into on Base?"
  • "Which Aave V3 tokens on Ethereum have the highest TVL according to Enso?"
  • "What is the price of WETH on Ethereum according to Enso?"

What it does

  • list_networks: List the blockchain networks Enso supports with chain id and name, optionally filtered by name or chain id.
  • list_projects: List the DeFi projects (for example aave, uniswap, morpho) Enso integrates with, with the chains and protocol slugs of each.
  • list_project_protocols: List the protocols (versions and forks) that belong to one DeFi project, with description, link and supported chains.
  • list_protocols: List every protocol Enso supports with its project, name, description and the chains it is available on, optionally for one chain or slug.
  • list_tokens: List base and DeFi tokens Enso knows about (vault, lending and LP tokens included) with APY, reward APY and TVL, filterable by chain, project, protocol, type and minimum APY or TVL. Pages of up to 1000 are cut to the first items.
  • get_token_price: Get Enso's USD price for one token on one chain, with decimals, symbol, timestamp and a confidence score.
  • list_aggregators: List the swap aggregators Enso can route through, optionally for one chain.
  • get_protocol_standard: Get the actions (deposit, redeem, borrow, swap and so on), function names, inputs and supported chains Enso offers for one protocol slug, plus its forks.
  • get_layerzero_pool: Look up the LayerZero Stargate pool address for a token on a chain, optionally with the pool on a destination chain. Returns null when no pool exists.

BYOK key

You bring your own Enso Enso API key (https://developers.enso.build). 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.enso.build 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.

Notices

Reference and price data only: no routing, bundling or transaction-building calls, and no wallet balances. The default rate limit is 10 requests per second.

Data sources

Live from the Enso API (api.enso.build) with a BYOK key; documentation: https://docs.enso.build/pages/api-reference/overview. 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 Enso. Enso 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 Enso account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Enso (BYOK) — Privacy Policy

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

What Enso (BYOK) is. Enso (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Enso data: Browse Enso's DeFi reference data (supported networks, protocols, DeFi and base tokens with APY and TVL, token prices, bundle standards and LayerZero pools) with your own API key. You bring your own Enso Enso API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Enso 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.enso.build, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Enso 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 Enso receives. The request we make on your behalf, including the key and the arguments, under Enso's own terms and privacy policy. Enso acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Enso 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 Enso 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. Enso (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 Enso at any time to end all access.

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

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

Terms of service

Back to top

Enso (BYOK) — Terms of Service

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

  1. The Service. Enso (BYOK) provides: Browse Enso's DeFi reference data (supported networks, protocols, DeFi and base tokens with APY and TVL, token prices, bundle standards and LayerZero pools) 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 Enso credentials and only access data you are allowed to access. Enso's terms apply to your use of Enso; 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 Enso. Enso 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 Enso returns, lightly trimmed; it may be incomplete, delayed or changed by Enso. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Enso 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 Enso'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; Enso 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 Enso 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 Enso 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-enso

Enso (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. Enso (BYOK) never asks for them.

Get Enso (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Enso Enso API key. Create one at https://developers.enso.build, 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 Enso. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Enso.