UniSat (BYOK) — connector documentation
- MCP endpoint:
https://byok-unisat.connectorbay.com/mcp - REST API:
POST https://byok-unisat.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-unisat.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own UniSat UniSat API key (free plan: 5 calls per second, 2,000 per day), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-unisat.connectorbay.com/health· Tool schemas:https://byok-unisat.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-unisat · agent@connectorbay.com
What UniSat (BYOK) is for
UniSat (BYOK) lets an AI assistant read your own UniSat data through the UniSat API with a key you supply (UniSat API key (free plan: 5 calls per second, 2,000 per day)). Read-only: 11 tools (get_blockchain_info, get_address_balance, get_address_history, get_transaction, list_block_transactions, get_inscription_info, list_inscription_events, list_brc20_tickers, get_brc20_info, list_brc20_holders, get_address_brc20_summary). 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 open-api.unisat.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by UniSat. UniSat 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 current Bitcoin block height on UniSat?"
- "What is the balance of this Bitcoin address?"
- "What are the latest transactions of this Bitcoin address?"
- "What are the details of this Bitcoin transaction?"
- "Which transactions are in Bitcoin block 840000?"
- "Who owns this ordinal inscription and what is its content type?"
What it does
get_blockchain_info: Get the Bitcoin chain state seen by UniSat: chain, block height, header height, best block hash, median time and chainwork.get_address_balance: Get a Bitcoin address balance in satoshis, split into plain BTC and satoshis held in inscriptions, with UTXO counts and pending amounts.get_address_history: List the transactions of a Bitcoin address, with ids, input and output totals, height, confirmations and time.get_transaction: Get one Bitcoin transaction by id: input and output counts and totals in satoshis, size, block height, confirmations and time.list_block_transactions: List the transactions of a Bitcoin block by height, one page at a time.get_inscription_info: Get an ordinal inscription by id: owner address, content type and length, inscription number, height, time and BRC-20 payload when present.list_inscription_events: List inscription events (creations and transfers) between two block heights, with inscription id, number, address and transaction.list_brc20_tickers: List BRC-20 token tickers known to the indexer, one page at a time.get_brc20_info: Get one BRC-20 token: creator, max supply, minted amount, mint count, holder count, decimals, limit per mint and deploy height.list_brc20_holders: List holders of a BRC-20 token with available, transferable and overall balance, one page at a time.get_address_brc20_summary: List the BRC-20 balances of a Bitcoin address with available, transferable and overall amount per ticker.
BYOK key
You bring your own UniSat UniSat API key (free plan: 5 calls per second, 2,000 per day) (https://developer.unisat.io). 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 open-api.unisat.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.
Data sources
- https://docs.unisat.io/developer-support/open-api-documentation (the API this connector calls, with a BYOK key)
Live from the UniSat API (open-api.unisat.io) with a BYOK key; documentation: https://docs.unisat.io/developer-support/open-api-documentation. 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 UniSat. UniSat 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 UniSat account.
Built for: Worldwide. Languages: English.