> For the complete documentation index, see [llms.txt](https://docs.fortemis.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortemis.io/venues.md). # Connecting venues ## Creating keys Create **read-only** API keys on each venue — no trade, transfer or withdrawal permissions. On venues whose consoles offer IP allow-listing, binding the key to the platform's egress address also removes key-expiry windows on some venues (e.g. Bybit's 90-day unbound expiry). ## Entering keys Administration → **Venue keys** in the client app. Each key is verified at save: the platform queries the venue's own key-permission endpoint and **rejects any key that can trade or withdraw**, with the reason shown. Venues that expose no permission introspection (Kraken, Bitget) require an explicit operator attestation checkbox, which is recorded. Stored keys are write-only — no interface exists to read one back. ## What happens next Within 30 minutes the full book appears: positions, balances, leverage and liquidation data. Instruments the platform has never seen **onboard themselves** — mapped from the venue symbol, price history backfilled, assigned the most punitive liquidity tier until a human reclassifies them (unknown assets look *worse*, never invisible). Unpriceable holdings land in the disclosed-exclusions register for review. Dust balances are ignored by rule. ## Key health An expired or revoked key marks that venue **degraded** — alerting the operators and the dashboard — while monitoring continues on the remaining venues. Replacing the key in the app restores the venue on the next poll. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.fortemis.io/venues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.