idapt Blog
Engineering
How idapt works under the hood, from the team building it.
Bring Your Own Keys: BYOK in Practice
How BYOK works in idapt: connect provider API keys, route matching models on your accounts, and mix BYOK with platform billing and local inference.
Connect Your Tools to idapt Over MCP
idapt is an MCP server: connect Claude Code, editors, or any MCP client and reach your Drive, agents, chats, and computers through the open protocol.
How Model Failover Works in idapt
The routing engineering behind 200+ models: cheapest-first provider selection, automatic failover, sticky conversation pinning, and visible attribution.
How We Rank 250+ Models
The methodology behind idapt's rankings: named public benchmarks, a rescaled capability index, live telemetry, and the rule against invented composites.
What 'Never Trained on Your Data' Means Technically
The engineering behind idapt's privacy stance: no training on user content, database-enforced isolation, a local-inference lane, and blocked AI training crawlers.
Real Receipts: How Model Outputs Are Captured
Why idapt's model showcases are captured from real production runs with cost and latency attached, and why staged demos are banned from proof surfaces.
Script Your Workspace: The idapt CLI
The idapt CLI drives your whole workspace from the terminal: chats, files, agents, computers, and generation, with five copy-paste recipes to start.
Build on idapt: SDK Quickstart
The @idapt/sdk in ten minutes: authenticate, chat with any model, read and write Drive files, and run agents from TypeScript.
Use 200+ AI Models with the OpenAI API Format
Point any OpenAI SDK at idapt's compatible endpoint and reach Claude, GPT, Gemini, and 200+ more models through one base URL, one key, one bill.