Skip to content

SandBase Docs

Build with Models and APIs directly, or define reusable Agents that run on managed infrastructure.

SandBase provides two complementary ways to build AI applications. Start with the smallest surface that fits the work; you can combine them as the application grows.

Choose how to build

Models and APIsManaged Agents
What it isDirect access to language, image, video, audio, embedding, and third-party APIsReusable, versioned Agent configurations executed by SandBase
Best forCustom application loops and fine-grained request controlMulti-step, asynchronous, scheduled, or repeatable work
You managePrompts, orchestration, retries, and application stateAgent definition, enabled capabilities, inputs, and delivery behavior
Start hereModels and APIsBuild Agent

One SandBase API key

The same API key can call Models, APIs, Agents, Endpoints, and scheduled workloads. Keep keys on the server and never expose them in browser code.

Core concepts

Models and APIs

Use Models for language, image, video, audio, and embedding workloads. Use APIs when the application needs external data or actions. The Store shows available capabilities, pricing, input schemas, and working examples.

Agents

An Agent is a reusable, versioned configuration containing a Model, instructions, APIs, Skills, and credentials. Define it once, test it, and then choose how it should run.

Services and Sessions

A Service exposes a tested Agent to applications. Its API resource is an Endpoint. Invoking it creates or continues a Session whose session_id identifies the durable interaction.

Schedules, DeploymentRuns, and Sessions

Schedules execute an Agent later or repeatedly. Their API resource is a Deployment. Every trigger creates a distinct drun_* DeploymentRun and, on successful Session creation, links it to a new sess_* Session.

First steps

  1. Create an organization and API key.
  2. Choose a Model, API, or Agent from the Store.
  3. Make a direct request or define and test an Agent.
  4. Publish the Agent as an Endpoint when an application needs to invoke it.
  5. Add a Schedule when the work should run automatically.
  6. Review Sessions, errors, latency, and cost in the Console.

Operational guidance

Next steps