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 APIDefine 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.
PLATFORM OVERVIEW
Build, deploy, schedule, and monitor custom AI agents in a closed loop: every path starts from an Agent definition and ends in a Session.
01 / AGENTS
An Agent is a reusable, versioned task definition and capability combination, set up in five stages: Overview, Instructions, Model, Capabilities and Runtime.
02 / SERVICES
03 / SCHEDULES
04 / SESSIONS
A Session is one actual run and its continuing work context, not just a log line.
SOURCES
EACH SESSION SHOWS
Where appropriate, you can continue a Session with more instructions or stop a running task.
Starting messageSummarize this week's product news for our category.
AgentSearching recent sources and extracting the key announcements.
search.queryquery: "category product news this week"SHARED CAPABILITIES
Models, Instructions, Skills, MCP and real-world APIs, Runtime and Versions are defined once on the Agent and carried through Services, Schedules and Sessions.
| Capability | Agents | Services | Schedules | Sessions |
|---|---|---|---|---|
| Models | Default model | Optional override | Optional override | Model recorded |
| Instructions | Goal and rules | Inherited | Plus starting message | Followed in transcript |
| Skills | Attached | Inherited | Inherited | Used in turns |
| MCP / Real-World APIs | Connected | Inherited | Inherited | Calls and results |
| Runtime | Runtime profile | Inherited | Inherited | Runtime recorded |
| Versions | Versioned definition | Selected version | Agent run | Version recorded |
TEMPLATES
Start from a public Agent, make it yours, and move it through the same loop.
Find a public Agent or template in the Agent Store.
Adjust instructions, model and capabilities for your task.
Chat with it and review what it did.
Publish a Service or create a Schedule.
Review each run as a Session.
USE CASES
Three patterns built from the same modules.
Combine a model with search and extraction APIs to gather sources and return structured findings in a Session.
Agent · Search API · Extraction APIAttach an Agent to a Schedule with a starting message; each run creates a Session with its report.
Schedule · Skills · Real-World APIsPublish a tested version as a Service and call it from your product; each invocation starts its own Session.
Service · Model · MCP ToolsFAQ
What teams ask before they build and run AI agents on SandBase.
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.
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.
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.
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.
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.