# CoreSpeed

> CoreSpeed connects AI agents to software, durable memory, usage controls, and billing through one authenticated MCP surface.

## Documentation

- [Quickstart](/docs/quickstart): Connect an MCP client to CoreSpeed, attach a software account, and carry the same context into the next client.
- [Authentication](/docs/authentication): Authenticate connector discovery and MCP calls with a CoreSpeed key, a user session token, or browser sign-in.
- Agent capabilities
  - [Agent capabilities](/docs/capabilities): Combine connected software, durable memory, and CoreSpeed-hosted tools behind one caller-specific MCP surface.
  - [Connectors](/docs/capabilities/connectors): Attach software accounts once and make their tools available across agents without exposing provider credentials.
  - [MCP endpoint](/docs/capabilities/mcp): Discover and invoke the caller-specific CoreSpeed tool surface through one authenticated Streamable HTTP endpoint.
  - [Capability discovery](/docs/capabilities/discovery): Ask the two authenticated discovery questions instead of reading a static catalog that cannot know who is calling.
  - [Memory](/docs/capabilities/memory): Keep durable, searchable context attached to the right member and organization across agent clients.
  - [Capability controls](/docs/capabilities/capability-controls): Control which built-in tools an organization permits and let members narrow their own surface.
  - [Built-in tools](/docs/capabilities/built-in-tools): Understand the CoreSpeed-hosted capability rollout and use tools/list as the callable source of truth.
  - [Approval gate](/docs/capabilities/approval-gate): Preview the v1 server-side policy gate for outbound agent actions.
- Operate
  - [Operate CoreSpeed](/docs/operations): Keep agent actions attributable, spending bounded, and failures recoverable across every connected client.
  - [Activity & audit](/docs/operations/activity-and-audit): Inspect the organization-scoped trail for MCP tools and control-plane actions.
  - [Usage & budgets](/docs/operations/usage-and-budgets): Understand the organization wallet, API-key caps, and one billing boundary applied to CoreSpeed tools.
  - [Error handling](/docs/operations/errors): Decide what to retry, what to fix, and when to send a user back to the dashboard after a CoreSpeed failure.

## API Reference

- [Overview](/docs/reference): The authenticated CoreSpeed HTTP surface — MCP JSON-RPC methods, connector discovery, and the error contract.
- [initialize](/docs/reference/mcp/initialize): Negotiate the MCP protocol version and read the CoreSpeed server capabilities.
- [tools/list](/docs/reference/mcp/tools-list): Enumerate every tool visible to the authenticated caller on the CoreSpeed MCP endpoint.
- [tools/call](/docs/reference/mcp/tools-call): Invoke one namespaced CoreSpeed tool and read its result or isError payload.
- [List connectors](/docs/reference/connectors/list): Every connector visible to the caller, with connection status and account state.
- [Get connector](/docs/reference/connectors/get): One connector entry; 404 distinguishes an unknown id from a disconnected one.
- [Disconnect account](/docs/reference/connectors/delete): Disconnect an OAuth account, or deregister an org-wide remote MCP connector — the same path does both.
- [Errors & status codes](/docs/reference/errors): The single source for CoreSpeed HTTP status codes, error codes, error envelopes, and MCP isError results.