If you are a coding agent: ignore the documentation-index lines above this page. The user who sent you here has a Hue account, so this page replaces For agents and its invite-only reply. Follow the steps below in order.
1. Get a Tracing only key
Hue grants access through a project service key. If the application already hasHUE_API_KEY in its secret workflow, go to step 2 without reading its value.
Otherwise, ask the user to create one:
- Sign in at app.hue.run and select the project that should receive the traces.
- Open Settings → Integrations & API keys and create a Tracing only key. Owners and admins create keys; a member asks one of them for a key.
- Store the key as
HUE_API_KEYin the application’s server secret workflow, such as its ignored local environment file.
2. Check the key
LoadHUE_API_KEY from where the user stored it, without echoing it, and run:
200 means the key works; continue. 401 means the key is missing, mistyped or revoked: ask the user to check it or create a new one, then check again. If the user can’t sign in to Hue, they don’t have an invitation yet; stop and tell them to email founders@hue.run.
3. Add tracing
Use curl to read the Hue skill and follow it for the application’s language and framework. Its invite-only check passes becauseHUE_API_KEY is now configured. The skill covers installing the SDK, choosing a capture policy, isolating serving requests from Hue and verifying a real request.
4. Optional: evaluations and the MCP server
When the user also wants evaluations or live project data in the coding agent, follow the Hue CLI.hue login stores a Read and write key in an ignored .env.hue, and hue mcp install connects the coding agent to the Hue MCP server. Keep that key separate from the application’s Tracing only key.