Run Rose 1 from curl before you create an account.

No-key demo call

This capped route is built for quick evaluation. It does not require signup or an API key, and it returns the same core output and receipt shape as production compression.

curl -s https://api.adola.app/v1/demo/compress \
  -H 'content-type: application/json' \
  --data '{
    "model": "rose-1",
    "query": "What does finance need before approving the rollout?",
    "input": "Customer account: Acme Logistics. The buyer asked whether invoices can be split by region. Support policy says enterprise workspaces may export region-level billing CSVs. Current blocker: the finance team needs API usage by project before approving the Q3 rollout.",
    "compression": { "target_ratio": 0.35, "preserve_order": true }
  }'

Production call

After creating a workspace, keep the same request body and add a project-scoped bearer key. Store the receipt next to the model request for cost and quality review.

curl -s https://api.adola.app/v1/compress \
  -H 'content-type: application/json' \
  -H "authorization: Bearer $ADOLA_API_KEY" \
  --data '{
    "model": "rose-1",
    "query": "What does finance need before approving the rollout?",
    "input": "Long retrieved context, ticket history, policy text, or agent trace...",
    "compression": { "target_ratio": 0.35, "preserve_order": true }
  }'

What to check

• Start with the capped no-key endpoint before creating a workspace.
• Use the same model, query, input, and compression fields in production.
• Compare output, tokens saved, compression ratio, and latency from the receipt.
• Move to bearer-key calls only after one real context block looks useful.