Skip to main content
Configuration → Credentials is where you give agents access to models and to the outside systems they operate on.

​
Model providers

By default agents run on OpenHive’s routed model pool, which draws on your bundled allotment. Adding your own provider key bypasses that allotment — you pay the provider directly and stop consuming bundled credits.
If you run high-volume work — large prospect lists, bulk enrichment — a DeepSeek or Groq key is usually the cheapest way to scale it.

​
Tool and data credentials

The same page holds credentials for the systems your agents act on: CRMs, data warehouses, databases, and email delivery. Each entry lists exactly which fields it needs — an API key, or a full connection (host, port, database, user, password). The catalog is broad and still growing. Entries OpenHive can’t yet complete a connection for are shown with Connect disabled, so you can see what’s coming without starting a flow that won’t finish.

​
Multiple accounts

A provider can hold more than one credential — use Add another account when you need separate keys for separate workspaces or clients.
Credentials are stored for use by the local runtime on your machine. Treat the machine running OpenHive as you would any machine holding production API keys.