SAGEA LogoDocs & API
Models & Pricing

Choosing a Model

Match models to your task, latency, and cost targets. All models are called through one base URL:

https://api.sagea.space/v1

Quick Selection Guide

Generalist models (text, reasoning, coding, agents)

ModelBest forContextLicense
SAGE 2.4 ActusFrontier agentic + coding, multimodal128kModified MIT
SAGE 2.5 CelerFast instruct/reasoning/coding in one model32kApache 2.0
SAGE OSSSelf-host, fine-tune, research (7B/14B/24B)16kApache 2.0

Specialized models (audio, OCR)

ModelBest forPricing
Sonus TTSTTS + zero-shot voice cloning, 30+ languages$15 / 1M chars standard
ARVA OCRDocument AI, tables, handwriting, 150+ languages$1.00 / 1,000 pages

Decision Framework

1. Define Your Use Case

Complex reasoning / agents / coding: Choose SAGE 2.4 Actus. 72B, 128k context, function calling, structured outputs, /v1/agents.

curl -X POST https://api.sagea.space/v1/chat/completions \
  -H "Authorization: Bearer $SAGEA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "sage-2-4-actus", "messages": [{"role": "user", "content": "Analyze the implications of quantum computing on cryptography"}]}'

High-throughput / cost-sensitive: Choose SAGE 2.5 Celer. 24B, 32k context, 3x faster at equivalent quality. $0.10 / $0.30 per 1M tokens.

Self-hosted / fine-tuning: Choose SAGE OSS. Open weights, LoRA + full fine-tune support.

Voice: Choose Sonus TTS for cloning + streaming at /v1/audio/speech. See Voice quickstart.

Documents: Choose ARVA OCR for layout-aware extraction at /v1/ocr/process. See Document quickstart.

2. Compare performance

RequirementActus 2.4Celer 2.5OSSSonus TTSARVA OCR
QualityHighestHighGoodStudio99.2% OCR
SpeedFastFastestFastestsub-200ms first byteFast batch
Context128k32k16k4k chars/input100MB/file
Cost$0.40/$1.20$0.10/$0.30$0.05/$0.15$15/1M chars$1.00/1K pages

Per-model rates are listed on each model card.

3. Evaluate Technical Constraints

  • Cloud-only: any model works.
  • Edge/mobile/offline: Celer or OSS for text; Sonus streaming for audio.
  • Real-time: Celer (chat) + Sonus stream (audio).
  • High throughput: Celer + batch at /v1/batch.

Cost Optimization

  1. Cache generated audio and repeated prompts.
  2. Use the right model: Celer for simple Q&A, Actus for reasoning.
  3. Batch processing: /v1/batch for thousands of requests.
  4. Right context: don't send 128k when 32k suffices.

Migration Strategies

  1. Test thoroughly: compare quality and latency in Foundry.
  2. Gradual rollout: A/B Actus vs Celer.
  3. Monitor metrics: latency, quality, cost per 1K requests.
  4. Fallback plan: keep previous model string as backup.

Getting Help

On this page