AI AGENT PLATFORM

Build and Run AI Agents on SandBase

Define an Agent with models, Skills and APIs. Test it in a Session, publish a callable Service or schedule recurring work, then inspect each run and its outputs.

AGENT PLATFORMILLUSTRATIVE UI
  1. 01
    AgentsDefine the work
  2. 02
    ServicesMake Agents callable
  3. 03
    SchedulesRun Agents automatically
  4. 04
    SessionsSee the actual work
Illustrative overview · not a live product embed.
  • Agents
  • Services
  • Schedules
  • Sessions

PLATFORM OVERVIEW

One Definition, Three Paths, One Record

Build, deploy, schedule, and monitor custom AI agents in a closed loop: every path starts from an Agent definition and ends in a Session.

  1. TEST PATH
    1. Agent Definition
    2. Test / Chat
    3. Session
  2. SERVICE PATH
    1. Agent Definition
    2. Publish Version
    3. Service
    4. Session
  3. SCHEDULE PATH
    1. Agent Definition
    2. Starting Message + Time Rule
    3. Schedule
    4. Session

01 / AGENTS

Agents: Define the Work

An Agent is a reusable, versioned task definition and capability combination, set up in five stages: Overview, Instructions, Model, Capabilities and Runtime.

Model
The default model the Agent uses. It is a swappable runtime choice, not a permanent binding.
Instructions
The goal and working rules the Agent follows.
Tools and Skills
Reusable Skills and tools that package steps for recurring tasks.
MCP Connections
MCP servers, including workspace MCP, that reach real-world APIs and systems.
Runtime Profile
The runtime the Agent's Sessions run in.
NEW AGENTILLUSTRATIVE UI
  1. 01
    OverviewName, purpose and description
  2. 02
    InstructionsGoal and working rules
  3. 03
    ModelDefault runtime model
  4. 04
    CapabilitiesTools, Skills and MCP
  5. 05
    RuntimeRuntime profile
ToolsSkillsMCPWorkspace MCP
Illustrative builder · not a live product embed.

02 / SERVICES

Services: Make Agents Callable

  • Expose a tested, selected Agent version as an HTTP Service.
  • Apps, app users, or AI tools can invoke it.
  • Each invocation creates a new Session.
  • A model override applies to new Sessions; leave it blank to inherit the Agent model.
SERVICEILLUSTRATIVE
Agent
Market Brief Agent
Version
v3 · tested
Model override
Blank — inherits Agent model
Callers
App · App user · AI tool
EACH RUN → New Session
Illustrative Service · sample values, no endpoint or request details shown.

03 / SCHEDULES

Schedules: Run Agents Automatically

  • A Schedule combines an Agent, a starting message, a time rule and a timezone.
  • It works without first publishing a Service.
  • Each scheduled run creates a Session.
  • A model override applies only to new Sessions; blank inherits the Agent default.
SCHEDULEILLUSTRATIVE
Agent
Market Brief Agent
Starting message
Summarize this week's product news for our category.
Time rule
Daily at 09:00
Timezone
Asia/Shanghai
Model override
Blank — inherits Agent default
EACH RUN → New Session
Illustrative Schedule · sample values, not a live configuration.

04 / SESSIONS

Sessions: See the Actual Work

A Session is one actual run and its continuing work context, not just a log line.

SOURCES

Direct / TestServiceSchedule

EACH SESSION SHOWS

  • Transcript
  • Events
  • Turns
  • Tool and MCP calls with results
  • Files and results
  • Agent, version, model, source, runtime and environment

Where appropriate, you can continue a Session with more instructions or stop a running task.

SESSION · ses_illustrativeMarket Brief Agent · v3
Status: Running
Source
Schedule
Model
Default model
Runtime
Runtime profile
TRANSCRIPT

Starting messageSummarize this week's product news for our category.

AgentSearching recent sources and extracting the key announcements.

EVENT · MCP tool callsearch.queryquery: "category product news this week"
Turn 2 · in progress
FILES / RESULTS
  • weekly-brief.md
  • sources.json
Illustrative Session · sample content, no live execution or measured result.

SHARED CAPABILITIES

One Set of Capabilities Across Every Module

Models, Instructions, Skills, MCP and real-world APIs, Runtime and Versions are defined once on the Agent and carried through Services, Schedules and Sessions.

CapabilityAgentsServicesSchedulesSessions
ModelsDefault modelOptional overrideOptional overrideModel recorded
InstructionsGoal and rulesInheritedPlus starting messageFollowed in transcript
SkillsAttachedInheritedInheritedUsed in turns
MCP / Real-World APIsConnectedInheritedInheritedCalls and results
RuntimeRuntime profileInheritedInheritedRuntime recorded
VersionsVersioned definitionSelected versionAgent runVersion recorded

TEMPLATES

From Template to Production

Start from a public Agent, make it yours, and move it through the same loop.

  1. 01

    Browse

    Find a public Agent or template in the Agent Store.

  2. 02

    Customize

    Adjust instructions, model and capabilities for your task.

  3. 03

    Test in a Session

    Chat with it and review what it did.

  4. 04

    Publish or Schedule

    Publish a Service or create a Schedule.

  5. 05

    Inspect Sessions

    Review each run as a Session.

USE CASES

What Teams Run on the Platform

Three patterns built from the same modules.

01 / RESEARCH

Research and Extraction

Combine a model with search and extraction APIs to gather sources and return structured findings in a Session.

Agent · Search API · Extraction API
02 / MONITORING

Scheduled Monitoring

Attach an Agent to a Schedule with a starting message; each run creates a Session with its report.

Schedule · Skills · Real-World APIs
03 / CUSTOMER-FACING

Customer-Facing Agent via API

Publish a tested version as a Service and call it from your product; each invocation starts its own Session.

Service · Model · MCP Tools

FAQ

AI Agent Platform Questions

What teams ask before they build and run AI agents on SandBase.

What is an AI Agent Platform?

An AI Agent Platform covers the full lifecycle of an Agent: defining it, testing it, making it callable, running it automatically and inspecting what it did. On SandBase these are Agents, Services, Schedules and Sessions.

How is it different from an AI Agent Builder?

An AI Agent Builder focuses on defining an Agent — its instructions, model and capabilities. The platform adds what happens next: publishing a version as a Service, running it on a Schedule, and reviewing every run as a Session.

What are Agents, Services, Schedules, and Sessions?

An Agent is a reusable, versioned task definition. A Service exposes a tested Agent version over HTTP. A Schedule runs an Agent from a starting message, time rule and timezone. A Session is one actual run and its continuing work context.

Can I change the model?

Yes. The Agent has a default model. Services and Schedules can set a model override for the new Sessions they create; leaving it blank inherits the Agent model.

How do Agent runs become Sessions?

Testing an Agent directly, invoking a Service and each scheduled run all create a Session. The Session records the transcript, events, turns, tool and MCP calls, files and results, plus the Agent, version, model and source.

Build Once.
Run Your Agent Anywhere.