Solutions engineering reference · from you.com/docs, reviewed Oct 26, 2026

You.com API Routing Matrix

Most evaluations that go sideways tested the wrong endpoint for the job. Start with what your code needs back: ranked results, page text, a cited answer, a researched report, or a model that grounds itself. Then copy the config for your use case.

ydc-index.io Web Search, Contents · header X-API-Key api.you.com Answer, Research, Finance, Images · header X-API-Key api.you.com Inference Router, MCP · header Authorization: Bearer

Start here: what does your code need back?

Answer this one question first. Every API takes the same key, so switching later is a URL and payload change, but an eval run on the wrong one measures the wrong product.

Use cases

One line per job. Click a row for the full request body, cost and what to avoid. Start with these defaults and add parameters only when the use case needs them.

Evals: match the benchmark to the endpoint

Run defaults first, then add one parameter at a time. Only compare against systems in the same latency class.

Latency classes:Web SearchContentssub-second retrieval·Answer~2.7s p50·ResearchFinance10s to 5 min
BenchmarkEndpoint and configCompare against

Why evals go off the rails

Check these before you trust a bad result.

Endpoint quick reference Host, auth, price and default rate limit
APIEndpointAuthPriceDefault limit