Routing
AgentCompile wraps your agent's model client. Known jobs run compiled. Anything new, unclear or unusual goes to your model, unchanged.
Your agent calls its model client, which the AgentCompile SDK wraps. A known job runs compiled, and the reply goes back to your agent without calling your model. Anything new, unclear or unusual goes on to your model provider, unchanged. If AgentCompile has any problem, or a step takes too long, the call goes straight to your model.
Four rules for every request.
Known jobs run compiled, your agent is always the fallback, nothing irreversible happens without a yes, and it fails open.
Three different requests run into one compiled job, and three identical answers come out. Your model stands beside it and is never called.
Your agent's model isn't called for them. AgentCompile learns the job, so it handles new customers, new orders and new details. A job goes live only after it gets your past conversations right.
A known request runs into the compiled job. A new one, carrying the conversation so far, turns off before the job and goes to your agent.
Anything new, unclear or unusual goes to your agent, unchanged. When AgentCompile hands a conversation back, your agent gets the whole conversation so far.
A change from the compiled job waits at a lowered bar. A yes arrives, the bar lifts, and only then does the change go through.
A compiled job asks your customer before it changes anything, and waits for their explicit yes.
The compiled job has a problem, so the request takes the path around it, straight to your model.
If AgentCompile has any problem, or a step takes too long, the call goes straight to your model.
If your company runs an AI agent in production, we'd like to compile its most repeated jobs with you.