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, Claude Skills, and the major agent frameworks. Every tool in this section wraps the same three APIs: Search, Contents, and Research. Switching between integrations is a transport change, not a capability change. One API key works across everything.

Choose your path

If you’re building with…UseWhy
Claude Code, Cursor, Windsurf, VS Code, or any MCP clientMCP ServerZero-config web access for your IDE or agent — free to start, no API key required
PythonPython SDKTyped client with async support, retries, and full Search / Contents / Research coverage
TypeScript or Node.jsTypeScript SDKFirst-class types, edge-runtime compatible, works in Next.js and Vercel AI SDK
Claude Agent SDK or Claude.aiSkillsDrop-in capability modules that give Claude grounded web search
LangChain, LangGraph, LlamaIndex, Vercel AI SDK, n8n, OpenAI GPT OSS, ZapierFramework integrationsNative tools and retrievers — no wrapper code required

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. Ships as a capability module Claude can invoke directly — works with the Claude Agent SDK and Claude.ai.

Use n8n or Zapier.

How it works

Every integration in this section hits the same three APIs:

  • Search — live-crawled web and news results with LLM-ready snippets
  • Contents — full page content extraction from URLs you already have
  • Research — multi-step synthesis for deep information gathering

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 everything

AI Frameworks

Developer Tools & SDKs

Automation Platforms

Official SDKs

Next steps