theorydelta field guide · v2026.04
built 2026-05-16 findings: 40 task hubs: 6 independent · evidence-traced · no vendor influence

I'M ABOUT TO… · TASK HUB

Choosing an LLM gateway

From picking a gateway to running it for real workloads — what fails between the docs and production.

FINDINGS 1
PHASES 4
LAST UPDATED 2026-03-22
PRIMARY TOOLS 3
EVIDENCE 1 empirical

PHASES

PHASE · PICK A GATEWAY

0 findings

No findings yet for this phase.

Coverage gaps are visible by design — Theory Delta surfaces what we haven't tested, not just what we have.

Tell us what you hit here →

PHASE · WIRE THE AGENT

0 findings

No findings yet for this phase.

Coverage gaps are visible by design — Theory Delta surfaces what we haven't tested, not just what we have.

Tell us what you hit here →

PHASE · RUN IN PRODUCTION

0 findings

No findings yet for this phase.

Coverage gaps are visible by design — Theory Delta surfaces what we haven't tested, not just what we have.

Tell us what you hit here →

FOR AGENTS · ASK BEFORE YOU WIRE

Your agent can pull this hub's findings as structured JSON.

Same content, machine-shaped. Wire your agent to query Theory Delta before it picks an MCP server, gateway, or framework — not after.

$ td query
td query "what fails when running LiteLLM as a budget gateway?"
→ 1 findings · 4 phases · last updated 2026-03-22
→ stream as Theory Delta MCP tool: list_findings(task="llm-gateway")
theorydelta.com · 2026 independent · evidence-backed · every claim sourced or labelled rss · mcp · /scan · llms.txt