Navige vs Respan API + MCP

Navige

Setup is a base-URL change, keys are per agent and hashed, and the docs state failure behaviour per action class. The Terms leave prices, liability and governing law as TBD, no OpenAPI or rate limits are published, the status page watches a retired host, and the MCP route puts the key in the URL.

Respan API + MCP

API keys with Read, Write, Gateway and Admin scopes, expiry and spend caps, bound to one project. 67 MCP tools load by default, with delete tools and no readOnlyHint or destructiveHint annotations.

Navige

1. Send the Navige key in x-navige-key on the proxy. Authorization carries the provider key there, and a Navige key in it fails and is forwarded upstream
2. Act only on allow or approved from /enforce. Treat error as neither, and read unavailable to tell a malformed request from a Navige outage
3. Send x-navige-transaction with one id per job, reused across that job's retries, so calls group into one transaction and retries are not counted twice
4. On a 429 from the proxy, check for a blocking budget before retrying. Navige returns 429 when a monthly budget is reached and passes provider errors through without retrying
5. Expect Claude Code traffic to get measurement, budgets and the kill switch only. Context trimming, routing, the output ceiling and prompt caching are switched off for it

Respan API + MCP

1. Create a key with only the Read scope for agents that analyse logs. New keys get Read, Write and Gateway by default
2. Set Respan-Enabled-Tools to a short list such as list_traces,get_trace_tree,list_logs. All 67 tools load otherwise
3. Pass filters to list_logs rather than paging through everything. The default window is the last hour
4. Call list_organizations first when results look empty over OAuth. Every tool acts on the active organisation only
5. Append .md to any docs URL for clean Markdown