> For the complete documentation index, see [llms.txt](https://docs.aloop.icustomer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aloop.icustomer.ai/settings/api-keys.md). # API keys API keys: what they are, how to get one, and how they behave. API keys let your own systems and agents authenticate to iCustomer. They are the credential behind the API and the MCP surface. ## Getting a key Keys are issued by your forward-deployed engineer. Email from your workspace's owner or admin account and say what the key is for. ## How keys behave * A key is shown **once**, at creation. Copy it then. Only a short prefix is displayed afterward. * A key has **full access** to your workspace, so treat it like an owner credential. * Keys are **revocable**, and can carry an expiry. * **Rotation is zero-downtime**: issue the new key, move your integrations over, then retire the old one. ## Keeping keys safe * Store keys in a secret manager, never in code or a shared document. * Rotate on a schedule, and immediately if a key may have been exposed. {% hint style="warning" %} **If a key is compromised**, revoke it right away through your forward-deployed engineer, then issue a replacement. Actions taken with the old key stay on record in your decision traces. {% endhint %} Everything the platform does is also available in the app, and your connected tools authenticate through [your stack](/integrations/stack.md), not API keys. Agents connect through [Bring your own agent](/iharness/bring-your-own-agent.md). --- # 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.aloop.icustomer.ai/settings/api-keys.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.