What it does
Navige is a proxy that sits between your AI agents and the model providers and tools they call. Every call is priced, recorded and grouped into the business job it belongs to; on a paid account, policies and budgets are enforced before a call runs, and cost levers such as caching, context trimming, loop guards and routing to a cheaper model cut spend. You connect it by changing a base URL.
Official source 1 ↗Features
- One-line LLM proxy. Point an existing OpenAI, Anthropic, Gemini or xAI client at Navige's base URL and add a Navige key header; your provider key is forwarded untouched and the provider's own response comes back, streaming included. Official source 1 ↗ · Official source 2 ↗
- Cost per business job. Tag calls with a workflow name, transaction id or W3C traceparent and Navige groups model calls, tool calls and retries into one job, reporting cost per job and, once you report outcomes, cost per successful job. Official source 1 ↗
- Cost levers. On a paid account, Navige can reuse a still-valid answer from cache, cap oversized tool results and trim history, block repeated failures, and route a step to a cheaper model based on task complexity. Official source 1 ↗
- Deterministic policies and approvals. Rules allow, deny or hold a call for a human, written against tool classes (read, write, destructive, financial, unknown) and agent autonomy levels L1–L5. The engine is plain code, not an LLM. Official source 1 ↗
- Kill switch and spend caps on every tier. Stopping an agent and hard spend ceilings work on the free tier too. Official source 1 ↗
- Recorded, modelled and measured numbers. Every figure is labelled as recorded (observed), modelled (a counterfactual estimate) or measured (a lever fired and both sides are known), and the three are never added together. Unknown model prices show as unknown, not zero. Official source 1 ↗
- Fail-open reads, fail-closed writes. If the gateway loses its own policy or budget state, reads and unclassified tools go through marked as degraded, while writes, destructive and financial actions are blocked; both are configurable. Official source 1 ↗
Pricing & free limits
Unlimited agents; every call priced and attributed, policy decisions recorded as advisory, a weekly modelled-savings report, plus the kill switch and spend caps. It does not change any traffic. No card. Official source 1 ↗ · Official source 2 ↗
Policies deny and hold calls and the cost levers act. If Navige saves you $45 or more in a month you pay $1 of every $5 saved; below that you pay a flat $9. Official source 1 ↗
Billing details
The share is taken only from measured savings, never from modelled estimates; if no lever fires, the bill is the $9 floor. The $9 counts towards the share in months where savings pass $45. Official source 1 ↗ · Official source 2 ↗
Cancelling returns the account to Watchtower without deleting data; policies that were denying calls become advisory again. Official source 1 ↗
Free access & limits
Watchtower only observes: policies are advisory and the cost levers do not act, so savings shown are modelled estimates, not money saved. Official source 1 ↗
Best for & limitations
Finding what one agent job actually costs, such as resolving a support ticket, instead of a raw count of model calls. Official source 1 ↗
Requiring human approval before an agent runs a write, destructive or financial tool. Official source 1 ↗
Measuring how much agent spend could be saved for free before deciding to let Navige change any traffic. Official source 1 ↗
- Paid tier has a $9 floor. Once savings are switched on you pay at least $9 a month, even if Navige saves you nothing. Official source 1 ↗
- Routing changes the model you asked for. On a paid account with levers on, a call may be answered from cache or sent to a cheaper model than the one your agent requested; each decision is recorded in the console. Official source 1 ↗
- Key revocation is not instant. Key lookups are cached for a minute, so a revoked key keeps working for up to that minute; the kill switch is immediate. Official source 1 ↗
- Costs are estimates of provider bills. Recorded cost is Navige's arithmetic over the provider's usage numbers, not the provider's invoice. Official source 1 ↗