Overview

Quickstart

This takes about five minutes — create a stack, generate a key, send your first request.

This takes about five minutes: create a stack, generate a key, send your first request.

1. Create a stack

From the dashboard, click New stack, give it a name, and pick a plan. The model that plan runs is assigned automatically — you don't need to pick one yourself unless you're on Enterprise.

2. Generate an API key

Open the stack, go to API keys, and create one. The plaintext key is shown once, at creation — copy it now.

.envbash
STAC_API_KEY=stac_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
STAC_BASE_URL=https://api.trystac.com/v1

3. Send a request

The model field is ignored — your stack always serves its own model, so any value works there.

bash
curl "https://api.trystac.com/v1/chat/completions" \
  -H "Authorization: Bearer $STAC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [{ "role": "user", "content": "Hello" }]
  }'

4. Stream the response

Add "stream": true to get tokens as they're generated, as server-sent events:

bash
curl "https://api.trystac.com/v1/chat/completions" \
  -H "Authorization: Bearer $STAC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [{ "role": "user", "content": "Hello" }],
    "stream": true
  }'

See Streaming responses for how to consume the stream in Python and Node.

Using an Anthropic-style client

If your tooling speaks the Anthropic Messages API instead (Claude Code, for example), point it at Stac the same way:

.envbash
ANTHROPIC_BASE_URL=https://api.trystac.com
ANTHROPIC_AUTH_TOKEN=$STAC_API_KEY

Requests to /v1/messages work with the same key, no separate setup.

Next steps