Realtime Register (BYOK)
Read your Realtime Register domain portfolio, DNS zones, credit balance, transactions and TLD rules with your own API key
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
Real questions, and the tools your agent calls to answer them.
list_networkslist_projectslist_project_protocolslist_protocolslist_tokensget_token_priceEnso (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.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://byok-enso.connectorbay.com/mcpThree ways in, the same 9 tools.
https://byok-enso.connectorbay.com/mcpPOST https://byok-enso.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-enso.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at developers.enso.build).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.
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.
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.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Realtime Register domain portfolio, DNS zones, credit balance, transactions and TLD rules with your own API key
Read your Rebilly billing customers, subscriptions, invoices, transactions, plans, products and coupons with your own secret API key
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
Read your Recharge subscriptions, charges, orders, plans, products and discounts with your own API access token
Read your Recurly accounts, subscriptions, invoices, transactions and plans with BYOK (US data center, API v2021-02-25)
Read your Recurly plan details, plan add-ons, items, coupons, measured units, shipping methods and price segments with your own private API key
https://byok-enso.connectorbay.com/mcpPOST https://byok-enso.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-enso.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-enso.connectorbay.com/health · Tool schemas: https://byok-enso.connectorbay.com/tools.jsonEnso (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:
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.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.
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.
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.
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.
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.
Effective 24 October 2026. These terms govern use of the Enso (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-enso.connectorbay.com/mcphttps://byok-enso.connectorbay.com/openapi.jsonWhen 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.