Skip to main content

Store batch

Store provides tenant-isolated, cross-thread long-term data outside checkpoint state. The batch endpoint accepts an array of StoreOperation objects:
Common kind values are get, put, delete, and search. The Store implementation validates operation-specific fields. Put dependent operations in one batch and interpret response results in request order.
namespace is slash-delimited and limit defaults to 10. Semantic query requires an Embedder; otherwise search follows the configured Store’s text/filter capabilities.

Schedules

POST/GET /v1/schedules creates/lists schedules. PATCH/DELETE /v1/schedules/{id} updates or deletes them. PATCH accepts cron, timezone, input, enabled, and metadata.
The Schedule API manages definitions. Confirm that your version/topology enables a cron executor. Without one, resources are stored but do not create runs automatically.

A2A and MCP

An assistant with mcp_expose: true in metadata is exposed as an MCP tool. The tool name uses mcp_tool_name, then name, then assistant ID. Gateways share the same tenant and RBAC boundary; remote results still pass through typed JSON serialization and schema validation.