Built-in tools
Understand the CoreSpeed-hosted capability rollout and use tools/list as the callable source of truth.
Built-in tools run on CoreSpeed-managed infrastructure and require no
third-party OAuth account. They share the same /mcp seam as connectors, so
identity, organization holds, API-key caps, activity recording, and capability
visibility still apply.
The authenticated engine inventory is not complete: GET /engines does not
exist yet. This page therefore does not publish a static engine catalog.
Use MCP tools/list; if a tool is absent there, it is not callable by the
current user and organization.
Available contract
Durable memory is documented as a stable seven-tool surface. Other built-ins
must be discovered from their live names and schemas in tools/list; do not
derive them from the retired public /catalog.
Seven durable-memory operations, free per call and still protected by the organization boundary.
The exact built-in names and schemas visible to the authenticated caller.
V0 rollout
Media and web are part of the v0 scope, but they are not yet public callable
surfaces. They remain hidden until their tools are mounted and returned from
tools/list.
| Capability | Intended surface | Current public status |
|---|---|---|
| Media | media__* image, video, and audio tools with model-schema discovery; signed artifact outputs | Validation / hidden |
| Web | web__search for ranked source material and web__scrape for one URL to clean Markdown | Validation / hidden |
Media calls will force safety controls and cap cost-driving parameters on the server. Web search will return source material rather than a second synthesized answer, and v0 scraping will be single-page only—no crawl queue.
These are product-shape commitments, not an assertion that the tools are
callable today. Their launch condition is simple: they appear in the
authenticated tools/list response.