Routescan (BYOK)

Routescan (BYOK) — connector documentation

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

What Routescan (BYOK) is for

Routescan (BYOK) lets an AI assistant read your own Routescan data through the Routescan API with a key you supply (Routescan API key (free registered plan is enough)). Read-only: 12 tools (get_balance, get_balances_multi, list_transactions, list_internal_transactions, list_token_transfers, get_token_balance, get_token_supply, list_token_holders, get_token_info, get_transaction_receipt_status, get_gas_oracle, get_block_number_by_time). 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.routescan.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Routescan. Routescan 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:

• "What is the AVAX balance of address 0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2 on Avalanche?"
• "What are the balances of these two addresses on Avalanche?"
• "What are the latest transactions of address 0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2 on Avalanche?"
• "Which internal transactions involve address 0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2 on Avalanche?"
• "Which ERC-20 transfers did address 0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2 make on Avalanche?"
• "How much USDC does address 0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2 hold on Avalanche?"

What it does

• get_balance: Get the native coin balance of one address in wei (AVAX on chain 43114, ETH on chain 1); divide by 10^18 for whole coins. The answer has status 0 and a message when there is nothing to return.
• get_balances_multi: Get the native coin balance of up to 20 addresses in one call (wei).
• list_transactions: List the normal transactions of an address (sent or received) with hash, block, time, parties, value, gas and error flag. Values are in wei. The answer has status 0 and a message when there is nothing to return.
• list_internal_transactions: List the internal transactions (value moved by contracts) that involve an address. The answer has status 0 and a message when there is nothing to return.
• list_token_transfers: List ERC-20 token transfers of an address, optionally for one token contract, with token name, symbol and decimals. The answer has status 0 and a message when there is nothing to return.
• get_token_balance: Get the ERC-20 token balance of an address in the token's smallest unit; divide by 10^decimals. The answer has status 0 and a message when there is nothing to return.
• get_token_supply: Get the total supply of an ERC-20 token in its smallest unit. The answer has status 0 and a message when there is nothing to return.
• list_token_holders: List the current holders of a token with their quantities, largest first as the API orders them. The answer has status 0 and a message when there is nothing to return.
• get_token_info: Get a token's type, name, symbol, total supply, website and social links. The answer has status 0 and a message when there is nothing to return.
• get_transaction_receipt_status: Check whether a transaction succeeded: result.status is 1 for success and 0 for failure.
• get_gas_oracle: Get the current safe, proposed and fast gas prices and base fee suggestion of the chain (in gwei).
• get_block_number_by_time: Find the block number mined closest before or after a Unix timestamp (seconds). The answer has status 0 and a message when there is nothing to return.

BYOK key

You bring your own Routescan Routescan API key (free registered plan is enough) (https://routescan.io/docs/plans-and-limits/api-keys-and-pricing). 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.routescan.io 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

Public chain data only. Routescan answers with status 0 and a message when a query has no result. Free plans ask for a Powered by Routescan.io APIs mention when the data is shown publicly.

Data sources

• https://routescan.io/docs/api/etherscan (the API this connector calls, with a BYOK key)

Live from the Routescan API (api.routescan.io) with a BYOK key; documentation: https://routescan.io/docs/api/etherscan. 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 Routescan. Routescan 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 Routescan account.

Built for: Worldwide. Languages: English.

Routescan (BYOK) — Privacy Policy

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

What Routescan (BYOK) is. Routescan (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Routescan data: Read balances, transactions, token transfers, token holders and gas prices on Avalanche, Ethereum, Mantle, Blast and 20 other chains through Routescan's Etherscan-compatible API with your own key. You bring your own Routescan Routescan API key (free registered plan is enough); the assistant sends it to us with each request.

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

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

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

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

Routescan (BYOK) — Terms of Service

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

1. The Service. Routescan (BYOK) provides: Read balances, transactions, token transfers, token holders and gas prices on Avalanche, Ethereum, Mantle, Blast and 20 other chains through Routescan's Etherscan-compatible API with your own 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 Routescan credentials and only access data you are allowed to access. Routescan's terms apply to your use of Routescan; 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 Routescan. Routescan 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 Routescan returns, lightly trimmed; it may be incomplete, delayed or changed by Routescan. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Routescan 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 Routescan'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; Routescan 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 Routescan 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 Routescan 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-routescan

Routescan (BYOK) support

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

• MCP endpoint: https://byok-routescan.connectorbay.com/mcp
• REST API: https://byok-routescan.connectorbay.com/openapi.json
• Live status: https://byok-routescan.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. Routescan (BYOK) never asks for them.