Skip to main content
This guide takes you from signing in to viewing your first trace in the Caveman Cloud console. You need an existing upstream model provider account (for example OpenAI) with an API key.
Fastest path: let your coding agent do it. In the console, open Getting Started, then Send one request, and choose the option where your coding agent does the wiring. Caveman Cloud gives you a prompt with your gateway URL and a fresh Cave key to paste into your agent. See Connect your coding agent and Automated AI setup. The manual steps below are the alternative.
1

Sign in to the console

Open your Caveman Cloud console in a browser and sign in. Invited members land directly in the project they were invited to.
2

Create a project

From the console, create a new project and name it. The project is the scope for all traces, keys, and workloads you will inspect.
3

Create a Cave API key

Go to Gateway, Connect and generate a Cave API key. Copy the key value and the gateway URL. The gateway URL is the origin for your installation, with no trailing slash. For example: https://gateway.caveman.so.
Keep the Cave API key secret. It authenticates you to Caveman Cloud. It is separate from your upstream provider key.
4

Set environment variables

Export the key and gateway URL in your shell. Keep your upstream provider key available separately.
5

Configure your client

Point your OpenAI client at the gateway with a base-URL swap. Send the upstream provider key in the x-cave-upstream-key header when it is not stored in Caveman Cloud.
The x-cave-agent and x-cave-workflow headers label traffic for reporting. They do not grant access.
6

View the trace

Open Traces in the console and look for the request you just sent. You should see the model, tokens, latency, cost, and the agent and workflow labels you attached.

Next steps

Connect a Workload

Learn how to route production agent or application traffic through the Gateway.

Traces and Spend

Filter, search, and understand request-level cost and latency.

Query with SQL

Run read-only SELECT over your project’s requests, spans, and tool events.

Evaluations

Build test cases and evaluate candidate changes against your traffic.