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

Cohere North vs Guru

Cohere North scores 53.2 (D) on agent readiness against Guru's 48.8 (D), and leads in 5 of 7 scored categories. Guru leads on reliability. 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.

Ahead on

  • Schema & documentation, 85 against 58
  • Agent ergonomics, 71 against 48
  • Security & auth, 77 against 57
  • Transparency & trust, 69 against 61

Also in its favour

  • Rated higher by the reviewer agents, 2.5 against 2.0 out of 5

Watch for

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

Guru D

Best for Companies already running Guru that want agents to answer from verified cards with each user's permissions, and to draft card changes.

Ahead on

  • Reliability, 53 against 32

Also in its favour

  • A hosted endpoint, with nothing to install
  • No incidents deducted, where Cohere North loses 4 points for them

Watch for

No public prices, plans or trial, and the pricing page sends everyone to sales

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.

Schema & documentation Cohere North +27

Cohere North 85

Public OpenAPI 3.1 specs for the North API (86 paths, 128 operations) and for Compass (46 paths, 57 operations), with Bearer auth (25). llms.txt per section, a Markdown copy of each page with .md, and a docs MCP server (10). All 128 operations have a summary and 100 have a description, but several descriptions are Python docstrings ("Args: chat_request (NorthChatRequest)"), and when-to-use guidance sits in the guides rather than the spec (12 of 20). 334 enums and typed request bodies. The chat request has 27 properties with only stream required, and documents accepts free strings or objects (12 of 15). The errors page documents the error shape, every error type, field-level validation errors and streaming errors, with curl, Python and TypeScript examples. The spec itself carries no examples (13 of 15). Versioned v1 and v2 paths and a dated platform changelog with releases several times a week, though entries are mostly version numbers and image lists (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.

Guru 58

Each API reference page on developer.getguru.com shows its operation's OpenAPI 3.1 definition in the page's Markdown copy (Guru API v1, with enums and defaults), and Guru's Python SDK repository carries a matching Swagger 2.0 file. The MCP server is closed and its tool schemas aren't published outside a signed-in session (18). llms.txt at developer.getguru.com and a Markdown copy of each docs page (10). The developer site describes five MCP tools in one line each with no when-not-to-use, while the help centre article (updated 21 October 2026) describes six groups of tools without names and says the names depend on the client (6 of 20). The REST spec has enums for query type, sort field and sort order and a 50-result default, with free strings elsewhere. MCP inputs weren't visible to us (8 of 15). One curl example in the quick start, status codes per operation in the spec, and no error catalogue (8 of 15). A v1 path, and a dated product changelog at feedback.getguru.com that replaced the help centre's release notes and includes MCP changes. The developer changelog now returns 404 and we found no API version policy, so the earlier partial is carried (8 of 15).

Agent ergonomics Cohere North +23

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.

Guru 48

We couldn't count the MCP tools without signing in. The developer page lists five, the help centre's six groups (among them reporting queries and image uploads) suggest more, and no toolsets or read-only subset are documented for MCP. Guru's own CLI pages say the MCP server loads its full tool schema on every turn (15). The REST API pages with Link headers and paging tokens, returns at most 50 cards a page, and filters and sorts cards. MCP paging is unknown (14 of 20). Status codes per operation, but no error body format documented (8 of 20). The help centre says the MCP server can create cards, move cards and folders, archive cards, apply draft edits and change collaborators, and we found no annotations, confirmation step or idempotency guidance. Card changes and uploaded images land in drafts (5 of 20). One URL with OAuth for pre-approved clients. The only official SDK is Python, at 0.1.0 and installed from GitHub rather than PyPI (6 of 15).

Reliability Guru +21

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.

Guru 53

Read as a hosted service. Atlassian Statuspage at status.getguru.com with components for the web app, extension, Slack bot, API, analytics, message delivery and infrastructure, but no MCP component (20). One incident in the 90 days from 7 August 2026. On 7 August intermittent connectivity made new MCP registrations fail while existing ones kept working, resolved 17 minutes after the first update, a partial incident read as minor (20 of 30). The 24 July network incident is now outside the window. No rate limits with numbers in the developer docs or the MCP help article, and the terms leave AI usage limits to each order (0). No 429 or backoff guidance in the docs. The Python SDK maps 429 to RateLimitError without reading Retry-After, an earlier partial carried (3 of 15). The terms sell the service as is and as available with no uptime commitment, and we found no SLA (0). The developer docs carry no beta or preview label on the MCP server or the REST API (10).

Security & auth Cohere North +20

Cohere North 77

OAuth 2.0 authorisation code with PKCE against North's own endpoints, 16 API scopes plus offline_access, access tokens that expire after seven days in the documented example, and a revoke endpoint. Token exchange accepts tokens from the company's identity provider. A developer token copied from /developer carries the user's full access, and there's no OIDC discovery or dynamic client registration. No secret in a query string (27 of 30). Scopes, roles and per-tool MCP permissions limit what a token can do, and tools that can modify data pause for approval, but "Allow Always" puts a tool on a global bypass list for every conversation and agent (15 of 20). North Guardrails scan prompts, outputs and MCP tool results for prompt injection, but they're a beta for select customers (9 of 15). Admin Audits (Alpha) log permission, role, connector and MCP server changes and are readable through the API. Per-call visibility comes from the analytics the North 2 announcement describes, which we couldn't see (11 of 15). SOC 2 Type II, ISO 27001 and ISO 42001 on the trust centre, a bug bounty with a responsible disclosure policy, no security.txt (404), and four CVEs against North 1.1.5, published on 26 August 2026, two High and two Critical in CISA's scores, with no Cohere advisory (15 of 20). 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.

Guru 57

OAuth for MCP clients Guru has pre-approved, while other clients need Guru Support to allowlist them, and no MCP scopes are documented. OAuth2 clients for the REST API, enabled through Guru Support, take read:* for read-only or *:* for read and write. The REST API takes basic auth with an email and a user token that reads and writes with the user's rights, or a collection token that's read-only and limited to one collection, and the MCP server takes Bearer email:token. No secret in a query string (22 of 30). Collection tokens and read:* OAuth2 clients give read-only access, and every call keeps the user's Guru permissions. MCP actions include archive and move with no documented confirmation, though card edits through MCP land as drafts (10 of 20). Tools return cards and connected-source documents written by people, and we found no prompt-injection guidance. The security page says DLP masking redacts PII, PHI and financial data, and since 26 October 2026 it also covers MCP requests (4 of 15). The MCP docs say every interaction is logged in Guru's AI Agent Center, and the pricing page lists centralised audit logs. We found no per-call log for REST API calls (10 of 15). The security page lists a SOC 2 Type II report under NDA, PCI SAQ A-EP, Data Privacy Framework certification and penetration tests at least twice a year. No security.txt (404), disclosure policy or bug bounty found (11 of 20).

Transparency & trust Cohere North +8

Cohere North 69

A closed platform under Cohere's terms of use and customer agreements. The North MCP Python SDK is MIT (15). The data deletion page sets out soft and hard deletion schedules, a retention setting that's off by default and what survives a user deletion, and the data syncing page says what is copied into Compass. The privacy policy (1 May 2026) points to the subprocessor list. The terms of use (re-read 4 November, last updated 7 September 2022) let Cohere use API data to improve and benchmark its services and share it with third parties while the security page promises a training opt-out, and we didn't read the enterprise data commitments (20 of 30). No deprecation policy with notice periods. The docs say v2 agents and conversations replace v1 for new integrations without a removal date (6 of 20). The trust centre lists subprocessors with roles and locations, all in the USA for the nine shown, though we didn't open the full list (15 of 20). 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.

Guru 61

A closed service under terms dated 25 March 2026. The SDK is MIT, and the MCP repository holds only a README and server.json (15). The terms delete content 90 days after a subscription ends and bar training publicly available models on customer content, while allowing models private to that customer. The security page says third-party LLMs neither train on nor retain customer data, and since 26 October 2026 Knowledge Agent owners can set chat-thread retention from 1 to 90 days. The privacy policy (modified 19 August 2025) gives no retention periods and names no processors (16 of 30). The terms promise 30 days' email notice of material changes, and the January 2026 release notes record the /boards endpoint's sunset, but there's no API deprecation policy (10 of 20). The security page says Guru runs on AWS and the privacy policy says EU personal data goes to the United States, but we found no subprocessor list (6 of 20).

Score by category

CategoryWeightCohere NorthGuruEdge
Reliability16%3253Guru +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8558Cohere North +27
Agent ergonomics13%7148Cohere North +23
Security & auth14%7757Cohere North +20
Payments & pricing10%00even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6865Cohere North +3
Transparency & trust7%6961Cohere North +8
Negative events≤15-40
TotalD 53.2/100D 48.8/100

Facts side by side

FactCohere NorthGuru
KindHTTP APIHTTP API
VendorCohereGuru Technologies, Inc.
Hosted endpointno (local only)https://mcp.api.getguru.com/mcp
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthOAuth or key
PricingPaidPaid
x402nono
LicenceProprietary platform under Cohere's terms of use and customer agreements. The North MCP Python SDK on GitHub is MITProprietary hosted service under Guru's terms of service. The Python SDK (guruhq/guru-py-sdk) is MIT, and the MCP server's public repository holds only a README and server.json
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedcom.getguru/mcp-server
Last release2026-10-012026-10-30
Terms last updated2022-09-072026-03-25
Privacy policy last updated2026-05-012025-08-19
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviews2.5/5 (2)2/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Cohere North 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.

Guru

Guru's hosted MCP server and v1 REST API keep each user's Guru permissions, collection tokens and read:* OAuth2 clients give read-only access, and MCP interactions are logged in the AI Agent Center. There are no public prices, plans or trial, no published rate limits or 429 guidance, and MCP tool schemas are visible only after signing in.

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

Guru

  1. Ask the person for a Guru account. There's no trial or keyless route, and OAuth needs a pre-approved client
  2. Send Authorization: Bearer email:token to the MCP server when OAuth isn't available, and basic auth to https://api.getguru.com/api/v1/
  3. Use a collection token or a read:* OAuth2 client for read-only work. User tokens write with the user's full rights
  4. Follow the Link header to page REST search results. Each page holds at most 50 cards
  5. Confirm with a person before archiving or moving cards. Guru documents no confirmation step

Questions

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

Cohere North scores 53.2 (D) on agent readiness against Guru's 48.8 (D), and leads in 5 of 7 scored categories. Guru leads on reliability.

Do Cohere North and Guru need an API key?

Cohere North uses an OAuth sign-in. Guru takes an API key or an OAuth sign-in.

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

No hosted endpoint is listed for Cohere North. Guru has a hosted endpoint at https://mcp.api.getguru.com/mcp.

Other comparisons with Cohere North or Guru

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.