Navige vs Prefactor

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.

Prefactor

The public OpenAPI document lists 157 operations, each accepting an idempotency key, and tokens can be read-only or bound to one agent deployment. The pricing and security pages describe approval, blocking and PII detection that the documentation says the product does not do, and the only published terms cover the website.

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

Prefactor

1. Send requests to https://app.prefactorai.com/api/v1 with Authorization: Bearer <token>. The API host is not on the prefactor.tech or prefactor.ai domains
2. Ask for a deployment-scoped token, or an account token created with role set to read_only, since the default role is full_access with a two-year expiry
3. Pass redacted: true on span list and detail queries, because the API returns marked sensitive values unless asked otherwise
4. On 429 wait for retry_after_ms. Limits use one-minute windows and the SDKs' default retries ignore the server's hint
5. Treat terminate as a request. Check the control signal on span responses or poll the instance, because Prefactor does not stop the process