Services

A Service makes a tested Agent callable from an application or AI tool. The underlying API resource is an Endpoint, so Service management and invocation use /v1/endpoints. One Service can expose REST, MCP, and experimental ACP according to its protocols setting.

When to create a Service

Create one when the Agent and its input contract are tested and an external caller needs a stable invocation URL. Keep editing and testing the Agent separately, then update the Service deliberately.

Invoke a Service

curl -X POST https://api.sandbase.ai/v1/endpoints/ep_01.../run \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"input":"Prepare a sourced customer brief."}'

Omit session_id to create a Session, or provide an existing authorized session_id to continue it. The response contains the persistent session_id and accepted Session events; it does not create a DeploymentRun.

Connect over MCP

When the Service includes the mcp protocol, use the mcp_url returned by the Endpoint API:

https://api.sandbase.ai/v1/endpoints/ep_01.../mcp

Send MCP JSON-RPC requests to that URL with the same SandBase API-key authentication. REST and MCP are protocols on the same Service; they are not separate published resources.

Product and API names

Product	API resource	API prefix
Service	Endpoint	/v1/endpoints
Schedule	Deployment	/v1/deployments

Next steps

• Service quickstart
• Endpoints API
• Sessions
• Schedules