quarry get an api key

scaled to zero

  1. request
  2. find a free gpu
  3. load the weights
  4. warm up
  5. first token

quarry, reserved

  1. request
  2. already loaded on your gpus
  3. first token
scaled to zero against reserved: each box is a step the request waits on. The reserved path has two.

the model waits, not you.

Open models on reserved GPUs, at one fixed price per million tokens.

already warm, every call.

Each deployment keeps its model loaded on its own reserved GPUs, so the first request answers like the hundredth.

example-project / deployments live
  • support-botwarm
  • search-rerankwarm
  • draft-writerwarm
  • new deployment

support-bot

warm
model
open-model-70b
gpus
4 reserved
cold start
0 s
rate
fixed per 1m tokens

promptWhere is my order?

It shipped this morning; the tracking link is in your inbox.

Recent requests to support-bot (sample)
timetokens intokens outstatus
09:41:0721258200
09:41:0318841200
09:40:5230496200

the rate holds at 3 a.m.

Traffic moves. The price per million tokens doesn’t.

a sample day of trafficyour price per million tokens

cold start

0s

The weights stay loaded between calls, so no request waits for a GPU.

price per million tokens

fixed

One figure for every token, whatever the traffic did.

A long aisle between black server racks under a white ceiling in a data centre
Reserved, never shared: the GPUs hold your model and nobody else’s.

one request, plain https.

To your own warm deployment. No client library to install.

curl https://api.example.com/v1/generate \
  -H "Authorization: Bearer $QUARRY_API_KEY" \
  -d '{ "deployment": "support-bot",
        "prompt": "Where is my order?" }'

response

{ "output": "It shipped this morning; the tracking
             link is in your inbox.",
  "usage": { "input_tokens": 212, "output_tokens": 58 } }
status
200
deployment
warm
cold start
0 s