Company API keys for AI chat: OpenAI and Anthropic

    Company API keys for AI chat: OpenAI and Anthropic - AI & Technology

    Chat inside Hice or a connected personal assistant

    There are two paths. In the first, use ChatGPT or Claude and connect Hice to work with accessible records. In the second, use chat inside Hice, with an administrator configuring the provider through an API key. The conversation's location and provider billing differ.

    Choose according to the team's work: who manages the provider, which users use chat and which operations are needed. Do not put a company API key in a prompt to connect a personal account. The external connector uses Hice authentication; API configuration belongs in the app's administrative settings.

    Use an OpenAI API key

    An administrator configures OpenAI in Hice's AI provider settings. Use a key from the API project or account intended for company work and verify the connection with the supported test. Then check the chat's selected provider before working with records.

    The key is not a ChatGPT password, and a chat subscription does not automatically fund API use. Configure provider spending controls and verify which account receives usage charges. Enter keys in the dedicated settings field rather than chat messages or candidate notes.

    Use an Anthropic API key

    To use Anthropic in Hice chat, an administrator adds the API key in AI provider settings and verifies the connection. The team then uses the provider according to the app's configuration. You need not transfer a personal Claude conversation to configure API access.

    Keep key ownership and usage clear. If switching providers, repeat a reading task and check handling of missing information before assigning an operational workflow. Using a different model does not change Hice permissions or make operations available when the chosen path does not expose them.

    Company configuration and user permissions

    Provider configuration is administrative: each user does not need to paste their own key. A company connection manages the provider in the workspace context. Before expanding use to the team, verify who can configure it, who can use chat and which records each role can access.

    The key enables the provider service rather than unrestricted Hice access. Try the same request with different users and check results against their permissions. If replacing the key, update it in settings and verify the connection before resuming activities.

    Chat subscriptions and API usage

    Hice's extension and connector are included; the AI provider can have its own costs. OpenAI API usage is billed separately from ChatGPT, as explained in OpenAI's billing documentation. Anthropic API use is also separate from a Claude subscription: see Anthropic's official explanation.

    Compare the Hice plan, any assistant subscription and API usage for your chosen path. 'Free integration' describes Hice's additional fee rather than promising unlimited tokens or free features in every provider.

    Tools to put the workflow into practice