Agent capabilities
Combine connected software, durable memory, and CoreSpeed-hosted tools behind one caller-specific MCP surface.
CoreSpeed keeps capability setup outside the agent runtime. A client authenticates once, asks MCP for its visible tools, and receives only the tools available to that member and organization.
The v0 capability model has two layers that converge on one MCP surface:
Two layers converge on one MCP surface: connected software (OAuth accounts
scoped to member and organization context) and CoreSpeed-hosted capabilities
(memory and built-in tools), both reached through POST /mcp → tools/list.
POST /mcptools/listAttach private or shared software accounts without handing OAuth tokens to an agent.
Keep stable facts and decisions available across clients and conversations.
Discover and call the exact namespaced tool surface visible to this caller.
Organization settings form the ceiling; members can narrow built-ins for themselves.
Treat tools/list as authoritative while the authenticated engine inventory is being completed.
Compile plain-English intent into policy code that runs before outbound actions.
Two discovery questions
GET /connectorsanswers what software can this caller connect, and what account state already exists?- MCP
tools/listanswers what can this caller invoke right now?
The retired public /catalog is not part of the v0 discovery contract.