# CoreSpeed > CoreSpeed connects AI agents to software, durable memory, usage controls, and billing through one authenticated MCP surface. To set up an agent, give it this line: `set up https://corespeed.io/SKILL.md`. The skill it fetches is [SKILL.md](https://corespeed.io/SKILL.md). ## When to use CoreSpeed Reach for CoreSpeed when an agent needs any of these, and you would rather not build them into the agent itself: - Act inside the apps a person has already authorized — Gmail, Slack, GitHub, Notion, Linear, HubSpot and more — without registering an API application or handling a key. The agent calls the connector's tools; CoreSpeed holds the OAuth grant. - Remember across sessions and across agents: memory is stored on the account, so a second agent (or the same one tomorrow) recalls what the first one saved. - Generate or analyze media, search and scrape the web, or research social platforms, through built-in tools with a fixed rate card. - Run unattended or for a team with a spend cap and a full activity log, so what it did and what it cost are on record. How to call it: connect an MCP client to `https://api.corespeed.io/mcp` (streamable HTTP; browser sign-in, or an API key for headless use) and the connected apps, memory and built-in tools appear as namespaced tools in `tools/list`. Details: [MCP server](/docs/mcp), [Authentication](/docs/authentication), [API reference](/docs/reference). ## Product pages, as Markdown Every page below also answers `Accept: text/markdown` at its normal URL. - [Product overview](/index.md) - [Pricing — plans and usage rates](/pricing.md) - [For Sales & Revenue](/for-sales.md): Research prospects, draft outreach, and log every touch to the CRM. - [For Marketing & Growth](/for-marketing.md): Ship campaigns, schedule social, and pull the funnel without copy-paste. - [For Customer Support](/for-support.md): Triage tickets, draft context-aware replies, and flag churn risk early. - [For Engineering & DevOps](/for-engineering.md): Triage the backlog, review PRs, and close out sprints from chat. - [For Finance & Operations](/for-finance.md): Categorize expenses, reconcile payouts, and close the month on autopilot. - [For Founders & Creators](/for-founders.md): Clear the inbox, book the calls that matter, and turn ideas into posts. - [Blog index](/blog.md) - [About](/about) · [Contact](/contact) ## Documentation - [Getting started](/docs): One MCP endpoint that carries your app connections, memory, media, and spending controls to every agent you run. Connect your agent once and it gets all of it. - [Authentication](/docs/authentication): Who is calling — a signed-in member, a member's API key, or an agent — and how each credential reaches CoreSpeed. - [MCP server](/docs/mcp): Connect any MCP client to CoreSpeed — one remote server with browser sign-in that carries your connected apps, memory, media, web, and social tools, with spend caps and an audit trail attached. - CLI - [CLI](/docs/cli): The cs command-line tool — sign in through the browser, mint API keys, write agent configuration, administer connectors and remote MCP servers, and call tools from a terminal. - [cs login](/docs/cli/login): Sign in to CoreSpeed through the browser and store the member session every other cs command runs under. - [cs whoami](/docs/cli/whoami): Show the signed-in user and the organization every cs command acts on. - [cs token](/docs/cli/token): Print a fresh session JWT to stdout for scripts and one-off requests. - [cs keys](/docs/cli/keys): Create, list, rotate, and revoke the sk-cs- API keys that act as you in agent configuration and CI. - [cs mcp-config](/docs/cli/mcp-config): Print an mcpServers block for the CoreSpeed MCP endpoint that carries your session token. - [cs connectors](/docs/cli/connectors): List connectors with your connection status, open a connect flow, and manage the accounts you have connected. - [cs remote](/docs/cli/remote): Register your organization's own MCP servers as remote connectors and administer their registrations. - [cs mcp](/docs/cli/mcp): Run tools/list and tools/call against the CoreSpeed MCP endpoint as yourself, to see and try what an agent will get. - [cs usage](/docs/cli/usage): Show the organization's available credit and plan from the terminal. - Connectors - [Connectors](/docs/connectors): Connect the apps your organization already uses — by OAuth, a pasted API key, or your own OAuth app — and let every agent act through it without holding the provider credential. - [Remote MCP servers](/docs/connectors/remote-mcp): Register your organization's own MCP servers and serve their tools through the same authenticated surface. - **Capabilities** - [Memory](/docs/memory): Keep durable, searchable context attached to the right member and organization across agent clients. - [Media](/docs/media): Generate images, video, and audio from a catalog of hosted models, and ask questions about media you supply — outputs arrive as signed artifact URLs. - [Web](/docs/web): Search the live web for ranked sources and turn one HTTPS page into clean text, with no search-provider account to connect. - [Social](/docs/social): Read public data from TikTok, Douyin, Xiaohongshu, Instagram, YouTube, X, and Reddit through typed, read-only tools — no platform account to connect. - [Capability controls](/docs/capability-controls): Narrow which built-in capabilities appear in your own tool list, and understand the organization-level ceiling above it. - **Operate** - [Activity & audit](/docs/activity): Inspect the organization-scoped trail for MCP tools and control-plane actions. - [Billing & credits](/docs/billing): Credits, the organization wallet, API-key spend caps, and the one billing boundary applied to every metered CoreSpeed tool. - [Approvals](/docs/approvals): The server-side policy gate for outbound agent actions — designed and shown in the dashboard, coming soon to the MCP surface. - [Error handling](/docs/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 covers both an unknown id and a connector this environment does not serve. - [Disconnect account](/docs/reference/connectors/delete): Disconnect your own private account on an OAuth connector. Remote MCP deregistration lives on its own path. - [manage__* tools](/docs/reference/tools/manage): The account-management tools on the MCP surface — API keys, agents, connected accounts, session, and remote MCP servers — with arguments and who may call each. - [Errors & status codes](/docs/reference/errors): The single source for CoreSpeed HTTP status codes, error codes, error envelopes, and MCP isError results. ## Blog - [A letter from our founders](/blog/a-letter-from-our-founders): Why we're building an operating system for agents, and what becomes possible when they have one. - [Introducing CoreSpeed](/blog/introducing-corespeed): An operating system for agents. - [How we took LongMemEval from 80.0 to 94.2 without touching retrieval](/blog/how-we-took-longmemeval-from-80-to-94-without-touching-retrieval): LongMemEval-S climbed from 80.0 to 94.2 while retrieval recall at 10 stayed at 0.99. The gains came from evidence budget, reader generation, and instructions. - [We retrieved the memory, then dropped the answer](/blog/we-retrieved-the-memory-then-dropped-the-answer): A 200-question conflict run scored 0.800 at the parent-Memory boundary and 0.635 at the evidence boundary. The gap was in what reached the reader.