Baserun vs Navige

Baserun

SDKs were MIT licensed and the Python source is still public at github.com/baserun-ai/baserun-py. Service offline since late 2024. api.baserun.ai doesn't resolve and app.baserun.ai serves an expired certificate.

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.

Baserun

1. Don't install baserun from PyPI or npm. Nothing answers behind it
2. Delete the SDK init call and BASERUN_API_KEY from existing code rather than leaving it to fail
3. Ignore docs.baserun.ai. It describes a service that no longer runs and doesn't say so

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