Integrations
Setup guides for every tool you use.
Already have a tool you love? Connect it to Hicap in minutes. Step-by-step setup for the tools you use every day, from AI coding agents to gateway proxies.
Pick your tool.
Local guides open directly on the page. External docs link out when the source of truth lives elsewhere.
05 guides in view
Source
Category
OpenClaude
Add Hicap as a custom OpenAI-compatible provider in OpenClaude and authenticate with the Hicap api-key header.
Install OpenClaude globally with npm
Open /provider and choose Add provider
Select Custom and enter the Hicap base URL and model
Use api-key as the auth header and leave the final API key field blank
Claude Code Router
Set up Hicap as a provider in Claude Code Router and route requests across OpenAI, Anthropic, Google, and other model families.
Install Claude Code and Claude Code Router globally
Create the router config and point it at api.hicap.ai/v1
Replace default auth with the required api-key header
Start the router and launch Claude Code through it
LiteLLM
Run LiteLLM in front of Hicap with explicit model aliases, local auth, and predictable routing for OpenAI-compatible workloads.
Create a .env file with HICAP_API_BASE, HICAP_API_KEY, and LITELLM_MASTER_KEY
Mount litellm_config.yaml and any override layer into the container
Define canonical provider-qualified aliases in model_list
Verify /models and a chat completion before wiring in your app
OpenClaw
Register Hicap as an OpenAI-compatible provider in OpenClaw and expose the exact models your team wants to use.
Add HICAP_API_KEY to your local environment
Register a Hicap provider with the Hicap base URL
Add the models you want to expose through OpenClaw
Map agent defaults and restart the gateway to verify
Cline VS Code and CLI
Use Hicap through Cline with BYOK provider settings in either the VS Code extension or the CLI.
Install the Cline extension or CLI
Choose BYOK as the provider mode
Select Hicap from the provider list
Paste your Hicap API key and start prompting
Requests
Request the next guide.
If your team uses a tool that is not covered here yet, contact us. We can help document the setup path or prioritize the next guide.