Avalanche Data API (BYOK)

Avalanche Data API (BYOK) — connector documentation

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

What Avalanche Data API (BYOK) is for

Avalanche Data API (BYOK) lets an AI assistant read your own Avalanche Data API data through the Avalanche Data API API with a key you supply (AvaCloud Data API key (free account)). Read-only: 12 tools (list_chains, get_chain, list_latest_blocks, get_block, get_native_balance, list_erc20_balances, list_erc721_balances, list_address_transactions, list_address_erc20_transfers, get_transaction, list_latest_transactions, list_chains_for_address). 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 glacier-api.avax.network. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Avalanche Data API. Avalanche Data API 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 Avalanche chains does the Data API support?"
• "What is the native token and explorer of chain 43114?"
• "What are the latest blocks on Avalanche C-Chain?"
• "Show block 49889407 on Avalanche C-Chain"
• "How much AVAX does 0x71C7656EC7ab88b098defB751B7401B5f6d8976F hold?"
• "Which ERC-20 tokens does 0x71C7656EC7ab88b098defB751B7401B5f6d8976F hold on Avalanche?"

What it does

• list_chains: List the EVM chains the Data API indexes (Avalanche C-Chain and L1s) with chain id, name, VM, explorer URL, native token and status.
• get_chain: Get one chain's name, status, VM, explorer URL, RPC URL and native token.
• list_latest_blocks: List the latest blocks of an EVM chain, newest first, with transaction count, gas used and fees.
• get_block: Get one block by number or hash: time, transaction count, gas used and fees.
• get_native_balance: Get the native token balance (for example AVAX) of an address with its price and value in a currency.
• list_erc20_balances: List the ERC-20 token balances of an address with price and value; spam tokens are hidden by default.
• list_erc721_balances: List the ERC-721 NFTs an address owns with collection name, symbol and token id.
• list_address_transactions: List the native transactions of an address (sent or received) newest first, with status, parties, value and gas.
• list_address_erc20_transfers: List the ERC-20 token transfers of an address with token, parties, value and transaction hash.
• get_transaction: Get one transaction by hash: status, parties, value, gas and fees (token transfers and logs are left out).
• list_latest_transactions: List the latest transactions on an EVM chain, optionally only failed or successful ones.
• list_chains_for_address: List the indexed chains where an address has activity.

BYOK key

You bring your own Avalanche Data API AvaCloud Data API key (free account) (https://developers.avacloud.io/data-api/getting-started). 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 glacier-api.avax.network 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

Read-only chain data from the vendor's OpenAPI file (data-api.yaml). An API key raises the rate limit; the free tier is weighted in compute units per minute and day. Amounts are in each token's smallest unit.

Data sources

• https://developers.avacloud.io/data-api/overview (the API this connector calls, with a BYOK key)

Live from the Avalanche Data API API (glacier-api.avax.network) with a BYOK key; documentation: https://developers.avacloud.io/data-api/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 Avalanche Data API. Avalanche Data API 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 Avalanche Data API account.

Built for: Worldwide. Languages: English.

Avalanche Data API (BYOK) — Privacy Policy

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

What Avalanche Data API (BYOK) is. Avalanche Data API (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Avalanche Data API data: Read Avalanche C-Chain and L1 blocks, transactions, token balances and transfers from the AvaCloud Data API (formerly Glacier) with your own API key. You bring your own Avalanche Data API AvaCloud Data API key (free account); the assistant sends it to us with each request.

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

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

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

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

Avalanche Data API (BYOK) — Terms of Service

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

1. The Service. Avalanche Data API (BYOK) provides: Read Avalanche C-Chain and L1 blocks, transactions, token balances and transfers from the AvaCloud Data API (formerly Glacier) 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 Avalanche Data API credentials and only access data you are allowed to access. Avalanche Data API's terms apply to your use of Avalanche Data API; 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 Avalanche Data API. Avalanche Data API 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 Avalanche Data API returns, lightly trimmed; it may be incomplete, delayed or changed by Avalanche Data API. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Avalanche Data API 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 Avalanche Data API'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; Avalanche Data API 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 Avalanche Data API 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 Avalanche Data API 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-avacloud-data

Avalanche Data API (BYOK) support

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

• MCP endpoint: https://byok-avacloud-data.connectorbay.com/mcp
• REST API: https://byok-avacloud-data.connectorbay.com/openapi.json
• Live status: https://byok-avacloud-data.connectorbay.com/health

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