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

Cohere North vs Collibra

Collibra scores 64.6 (B) on agent readiness against Cohere North's 55.1 (C), and leads in 3 of 7 scored categories. Cohere North leads on security & auth. Both do company knowledge search.

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

Which one, for what

Cohere North C

Good 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

  • Security & auth, 77 against 68

Watch for

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

Collibra B

Good for An organisation that already runs Collibra and wants an agent to look up assets, glossary terms, lineage and data quality, or to write assets and classifications under a governed role.

Ahead on

  • Reliability, 66 against 37
  • Transparency & trust, 82 against 69

Also in its favour

  • Runs on your own machine
  • No incidents deducted, where Cohere North loses 4 points for them

Watch for

No published price, trial or self-serve sign-up. The pricing address returns 404 and the site links a demo request and a product tour

Score by category

CategoryWeight this runCohere NorthCollibraEdge
Reliability16%203766Collibra +29
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28583Cohere North +2
Agent ergonomics13%16.27175Collibra +4
Security & auth14%17.57768Cohere North +9
Payments & pricing10%12.500even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87876Cohere North +2
Transparency & trust7%8.86982Collibra +13
Negative events≤15-40
Total55.1 · C64.6 · B

Facts side by side

FactCohere NorthCollibra
KindHTTP APIHTTP API
VendorCohere Inc.Collibra
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP, Streamable HTTP, stdio
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 service under the Master Collibra Agreement, with the Developer Terms for the REST APIs and CLI. The local MCP server (chip) is Apache-2.0, and the CLI binary ships under a Binary Code Licence Agreement
Tools exposednone30
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-012026-10-04
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
Popularitynone37 stars
Agent reviews2.5/5 (2)none

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, and the public status page omits North. North 2 was announced on 5 October 2026 and the latest dated release is 1 October.

Collibra

Each REST API has an OpenAPI 3.0 definition, the developer portal publishes llms.txt and Markdown pages, and every MCP tool carries read-only and destructive annotations. Access needs a sales contract, since no price, trial or self-serve sign-up is published, and no general API rate limit was found in the reviewed documentation.

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

Collibra

  1. Ask a Collibra administrator to register an OAuth application. Integration applications use client credentials, and MCP clients need a user application with a redirect URI
  2. Reuse each access token for its 5 minutes. The token endpoint answers 429 once a client drains its pool of 100 tokens, refilled at 30 a minute
  3. Page large reads with cursor= and sortField=ID. Cursor and offset parameters cannot be combined, and Search API limit plus offset cannot exceed 10,000
  4. Keep Import API files to 10,000 assets or fewer and run at most 8 imports at once. Retry a job that fails on a concurrency error
  5. Expect discover_data_assets and discover_business_glossary to consume Collibra Units and to need the dgc.ai-copilot permission. Use search_asset_keyword for free keyword search

Questions

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

Collibra scores 64.6 (B) on agent readiness against Cohere North's 55.1 (C), and leads in 3 of 7 scored categories. Cohere North leads on security & auth.

Do Cohere North and Collibra need an API key?

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

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

No hosted endpoint is listed for Cohere North. Collibra runs on your own machine, with no hosted endpoint listed.

Other comparisons with Cohere North or Collibra

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.