SDKs & tools overview

One API, every agent surface. Pick the integration that matches how you're already building.
View as MarkdownOpen in Claude

You.com meets your agents wherever they run—MCP clients, Python and TypeScript codebases, agent skills and plugins, and the major agent frameworks. Every tool in this section wraps the same four APIs: Search, Contents, Research, and Finance Research. Switching between integrations is a transport change, not a capability change. One API key works across everything.

Install our docs MCP server

This documentation ships with a Docs MCP Server that gives any MCP-enabled agent a searchDocs tool to search every page here and get back relevant passages with source URLs—no API key required. Point your client at https://you.com/docs/_mcp/server. See the Docs MCP Server guide for setup and examples.

Choose Your Path

Most Common Setups

Use the MCP Server. Five-line config, works with Claude Code and every major IDE. Run it locally without an API key to start, or connect to the remote server for OAuth 2.1 auth and higher rate limits.

Use the Python SDK or TypeScript SDK, depending on your stack. Layer in a framework integration if you’re using LangChain, LangGraph, or the Vercel AI SDK.

Use Skills. The same five skills run in Claude Code, Cursor, Codex, GitHub Copilot CLI, Kimi Code, OpenCode, OpenClaw, Pi, and Hermes. Install them with npx skills add youdotcom-oss/agent-skills or through your platform’s plugin path.

Use n8n or Zapier.

How It Works

Every integration in this section hits the same APIs:

  • Search—web and news results with LLM-ready snippets, plus optional highlights or full page content
  • Contents—full page content extraction from URLs you already have
  • Research—multi-step synthesis for deep information gathering
  • Finance Research—citation-backed answers from a finance-optimized index (available via MCP as you-finance)

That means:

  • You get the same data, the same filtering controls, and the same rate limits regardless of which integration you pick
  • Switching between MCP and the SDKs—or between frameworks—is a transport change, not a capability change
One API key works across every surface

You can start with MCP, move into an SDK, and add framework integrations later without changing the underlying API capabilities.

Integrations

Third-party framework, platform, and open-model integrations live on the Integrations page—crewAI, LangChain, LangGraph, LlamaIndex, Vercel AI SDK, Temporal, n8n, Zapier, OpenAI GPT OSS, and more as they ship.

Developer Tools

Official SDKs

Next Steps