Head to head · Company knowledge search · October 2026 research run

Cohere North vs Onyx

Onyx scores 65.4 (B) on agent readiness against Cohere North's 53.2 (D), and leads in 5 of 7 scored categories. Both do company knowledge search.

Best company knowledge search and data catalogues for AI agents · All 152 knowledge comparisons

Which one, for what

Cohere North D

Best for Regulated companies that want an agent and search platform over their own documents, mail and tickets, run privately or air-gapped and called through a REST or OpenAI-compatible API.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public price, trial or self-serve signup. Access starts with a sales conversation

Onyx B

Best for Teams that want one permission-aware index over Slack, Drive, Confluence, Jira, GitHub and the rest, self-hosted or air-gapped, with agents searching it through MCP.

Ahead on

  • Reliability, 72 against 32
  • Agent ergonomics, 77 against 71
  • Payments & pricing, 45 against 0
  • Maintenance & community, 77 against 68

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card
  • Open source
  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

Version 5.0.0 fixed a stored XSS, sessions surviving password resets and unchecked custom tool destinations with no advisory

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Onyx +45

Cohere North 0

Read with the hosted rubric, since Cohere sells North as a licensed platform whether it hosts it or the customer does. No x402, MPP or L402 (0). cohere.com/pricing says "Get in touch for custom enterprise pricing" for North (0). No North trial or free tier found. Cohere's trial API keys cover the models, not North (0). A person buys through sales, then an admin registers OAuth apps or a user copies a token (0). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Onyx 45

Scored on Onyx Cloud, as the rubric asks for open-source software with a paid version. No x402, MPP or L402 (0). Business is $20 a user a month billed annually on the public pricing page and Enterprise is by quote, plan pricing with no per-call unit (10). A two-week Cloud trial with no card, and the MIT Community Edition is free to run yourself (20). A person signs up in a browser and creates the token, on Cloud or on their own instance (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Reliability Onyx +40

Cohere North 32

Read with the hosted lines and scored on the Cohere-hosted North API that the quickstart uses (north.cohere.com). Private deployments run on the customer's own infrastructure. status.cohere.com is a public Statuspage, but the 5 October reading of its components came from its JSON API, which this method doesn't read, so it is struck, and the page isn't re-read under Cohere's terms (0). No readable incident history for North itself; the earlier incident reading came from the same JSON API (5). No fixed limits for the North API. Admins set request and token tiers per user and group through Flow Control, which is marked Alpha and needs a Helm setting before it applies (5 of 15). The errors page marks 429 and 503 as the only retryable errors, sends Retry-After and retry_after_seconds, and asks for exponential backoff with jitter capped near 60 seconds. No idempotency or safe-retry guidance for writes (12 of 15). The terms of use sell the service "as is" and "as available", and no North SLA was found (0). Chat, Responses and the agents API carry no beta label (10). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation.

Onyx 72

Onyx is mostly run self-hosted, and Onyx Cloud runs it for you, so we scored both halves and took the mean, as we did for Marmot. Self-hosted, on the local checklist. Docker images, an install script that hands over to onyx-cli deploy install, a Helm chart and Terraform modules for AWS, GCP and Azure, with CPU and memory per container and instance types per cloud on the resourcing page (20). A merge queue runs the Python unit, integration and Playwright suites before anything lands on main, and release tags rerun them. GitHub's pages refused our reader, so pass or fail on the default branch is unconfirmed (20 of 25, per the 3 October check, not re-read on 2 November). Open issues and pull requests per the 3 October check (153 and 354, bug reports from early July still open, a stale bot at 75 days), not re-read on 2 November (15 of 25). The docs commit to SemVer 2.0.0 and every changelog entry has a Deployment Changes section. v5.0.0 (23 October) put its removals in a major, but 4.7 moved permissions to groups and 4.9.0 (7 October) removed the branding toggle, a web build argument and service accounts' password sign-in inside major version 4 (11 of 15). Version 5.0.3 (15). That half comes to 81. Cloud, on the hosted checklist. A Better Stack status page at status.onyx.app with three monitors and 90-day bars (20). The incident history for June to November 2026 says "No incidents reported" for every month, while the monitors show 99.947 and 99.965 per cent for the functional frontend check and 99.985 and 99.990 per cent for the API server. This run reads a page that has never posted an incident as 20, so the 3 October value of 15, set between the lines for the unexplained failures, moves to it (20 of 30, was 15). Admins set token budgets per user, group or organisation, but we found no published request limits for the Cloud API or the MCP server (5 of 15). Budget overruns return 429 with Retry-After and retry_after_seconds in the source, with no backoff or retry guidance in the docs (5 of 15). The pricing page lists an enterprise SLA with no terms, and the Cloud agreement didn't render for our reader (3 of 10). The MCP server and the API carry no beta label (10). That half comes to 63. The mean of 81 and 63 is 72.

Maintenance & community Onyx +9

Cohere North 68

North Platform v1.15.4 on 1 October 2026 is the last dated API change recorded, 34 days before the check (20). The North 2 announcement of 5 October isn't shown to change the API. The North changelog had dated entries from 23 June to 1 October 2026, several a week, across parallel 1.12, 1.13, 1.14 and 1.15 release lines, three or more of them since 6 August (20). A closed service with a public dated changelog, a support bundle procedure and a Cohere Discord. Changelog entries are mostly version numbers and container image lists, and we didn't test support (10 of 15). Official SDKs for Python, TypeScript and Go are current with the platform but aren't published to PyPI or npm, and the Go SDK repository isn't public (a clone asks for credentials) (12 of 15). The North MCP Python SDK is at 0.4.5 (16 July 2026) with its last commit on 29 July 2026, and its README installs it over git+ssh (6 of 10). The changelog and docs are per the 5 October check, not re-read on 4 November under Cohere's terms.

Onyx 77

v5.0.3 tagged on 30 October 2026, with 4.9.6 on 29 October (30). Six minor or major releases since 4 August (4.5.0 on 4 August, 4.6.0 on 20 August, 4.7.0 on 4 September, 4.8.0 on 18 September, 4.9.0 on 7 October and 5.0.0 on 23 October by the changelog's dates) and 122 stable 4.x and 5.x tags in all (20). Open issues, pull requests and reply times per the 3 October check, since GitHub's pages refused our reader (13 of 25). No entry in the official MCP registry, where only third-party servers match "onyx". Official clients are onyx-cli (tags up to cli/v1.4.4) and a Terraform provider (5 of 15). Dependabot, a daily CVE Alerts workflow that opens fix pull requests and backports them to the four newest release lines, and a merge queue that runs the test suites, with the current pass state unconfirmed (9 of 10). 30 + 20 + 13 + 5 + 9 = 77.

Agent ergonomics Onyx +6

Cohere North 71

Chat takes max_tokens, citation options, a truncation strategy and a stateless mode, but responses include raw_prompt and raw_generation fields that the quickstart strips by hand. The North API has no standalone search endpoint, and sized search results come from the separate Compass API (15 of 25). List endpoints take limit and offset, and Compass search takes limit and cursor (15 of 20). Errors carry error_type, a stable error_code, is_retryable, request_id and field_errors, mirrored in X-North-Error-Code (20). No idempotency keys. is_retryable tells a client which failures are safe to repeat, and North reads readOnlyHint and destructiveHint from the MCP tools it calls (8 of 20). Only stream is required on chat. Official SDKs for Python, TypeScript and Go, and the Open Responses endpoint works with the OpenAI SDK, but the Python and TypeScript SDKs install from each customer's instance (13 of 15). Per the 5 October check, not re-read on 4 November, because Cohere's terms of use (last updated 7 September 2022) bar data mining, robots and similar extraction methods on the Cohere website, API and related documentation.

Onyx 77

Three tools in 3,360 characters of descriptions (about 850 tokens), plus three resources that list sources, document sets and agents. All three tools only read, so there's nothing to subset (25). Search filters by source, document set, agent and an updated-since time, search_web takes limit (default 5), and open_urls caps a call at 20 URLs. Document search has no result limit or paging and returns full chunks, so the response size is the server's choice (14 of 20). Errors say what failed and list close matches, or the available values when there are ten or fewer, and an empty index gets its own message. They come back as ordinary results with an error field and an empty list, not as isError (16 of 20). No readOnlyHint or other annotations. Every tool reads, so a retry is safe, though each document search can run an LLM query-expansion step and spend model tokens again unless skip_query_expansion is set (12 of 20). Only query is required. The official clients are onyx-cli (a Go binary, also on PyPI) with an agent mode and JSON output, and a Terraform provider, with no Python or TypeScript library (10 of 15). 25 + 14 + 16 + 12 + 10 = 77.

Score by category

CategoryWeightCohere NorthOnyxEdge
Reliability16%3272Onyx +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8588Onyx +3
Agent ergonomics13%7177Onyx +6
Security & auth14%7773Cohere North +4
Payments & pricing10%045Onyx +45
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6877Onyx +9
Transparency & trust7%6969even
Negative events≤15-4-7
TotalD 53.2/100B 65.4/100

Facts side by side

FactCohere NorthOnyx
KindHTTP APIPlatform
VendorCohereDanswerAI, Inc. (Onyx, formerly Danswer)
Hosted endpointno (local only)https://cloud.onyx.app/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary platform under Cohere's terms of use and customer agreements. The North MCP Python SDK on GitHub is MITMIT (Community Edition, including the MCP server, the API server, the CLI and the connectors). Code under the ee directories is under the Onyx Enterprise License, which needs a subscription for production use
Tools exposednone3
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-012026-10-30
Terms last updated2022-09-07couldn't be read
Privacy policy last updated2026-05-01couldn't be read
Customer content may train modelsyescouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone32k stars
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Onyx higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Cohere North

North has a public OpenAPI 3.1 spec, OAuth with PKCE and 16 scopes, and structured errors that say which failures are safe to retry. Access is the main limitation. Pricing is by sales only, with no trial, no North status history could be read and no SLA was found. The latest dated release found is v1.15.4 of 1 October 2026.

Onyx

MIT Community Edition, MCP server included and on by default since 5.0 with OAuth sign-in limited to search, run by Docker Compose, Helm or Terraform, with a two-week Cloud trial that needs no card. Version 5.0.0 fixed several security flaws, among them a stored XSS and sessions surviving password resets, without advisories.

Before you call either

Cohere North

  1. Get the North host from your admin and call https://<host>/api. Cohere-hosted examples use north.cohere.com
  2. Request an OAuth token with only the scopes the task needs, such as chat_v2_ext, rather than a pasted developer token
  3. Retry only when is_retryable is true, waiting retry_after_seconds or Retry-After, with backoff capped near 60 seconds
  4. Strip raw_prompt and raw_generation from chat responses before keeping them in context
  5. Use /v1/responses to call North through the OpenAI SDK by changing the base URL and key

Onyx

  1. Get the instance URL from the operator. Cloud is https://cloud.onyx.app/mcp, and self-hosted servers answer at /mcp/ by default from 5.0
  2. Prefer the OAuth sign-in or a token limited to read:search. Either covers every MCP tool and nothing else
  3. Pass time_cutoff as a full ISO 8601 timestamp. A value that doesn't parse is dropped and the search runs unfiltered
  4. Check each result for an error field. Failures come back with an empty results list, not as tool errors
  5. Expect a new token after a password reset. Since 5.0 a reset revokes all of that user's personal access tokens

Questions

Which is better for AI agents, Cohere North or Onyx?

Onyx scores 65.4 (B) on agent readiness against Cohere North's 53.2 (D), and leads in 5 of 7 scored categories.

Can an agent call Cohere North and Onyx without installing anything?

No hosted endpoint is listed for Cohere North. Onyx has a hosted endpoint at https://cloud.onyx.app/mcp.

Are Cohere North and Onyx open source?

No open-source release is listed for Cohere North. Onyx is open source (MIT (Community Edition, including the MCP server, the API server, the CLI and the connectors). Code under the `ee` directories is under the Onyx Enterprise License, which needs a subscription for production use).

Other comparisons with Cohere North or Onyx

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.