# AI and API across your whole company, not one silo

> Because every Cordango capability writes to the same organizations and people, an assistant can answer questions that cross them. REST and MCP reach the whole company under the same permissions as a person.

Source: https://www.cordango.com/ai/
Language: en

AI & API

# Your whole company, legible to AI.

An assistant is only as useful as the data it can reach. Most companies can point one at a single tool. Cordango can point one at the company, because the capabilities already share the same records and the same permission model.

[See Cordango in action →](https://www.cordango.com/company-graph/) [Why this is hard elsewhere →](https://www.cordango.com/ai/#why)

## The hard part was never the model.

— why this is hard elsewhere

Connecting an assistant to one SaaS tool is easy and mostly useless, because the interesting questions cross tools. Which customers are unhappy and up for renewal. Who is available next month and has done this kind of work before.

Answering those elsewhere means building a data layer first: connectors, a warehouse, a semantic model, and a permission story you have to invent twice. Cordango already has one data plane with one permission model, so the assistant has something coherent to read.

-   ONE One data plane, so cross-capability questions are ordinary
-   RBAC The assistant inherits your permissions, it does not bypass them
-   LIVE Reads current records, not a nightly copy
-   TRACE What it did lands in the same audit history as everything else

Cordango AI Organizations + CRM + Invoices

\# ask across the company > which trial customers have an overdue invoice? → Globex SE €4,200 · 9d · owner Tomas R. → Umbrella Co €1,150 · 3d · owner Lena K. ✔ pulled live from 3 capabilities · CRM · Invoices · Organizations ✔ your permissions applied · you see what you may see

## Reachable in three ways.

The same company, the same permissions, three doors in.

MCP 

#### MCP server

Point an MCP-speaking assistant at Cordango and it can read and act across your capabilities, under the acting user’s permissions.

REST 

#### REST API

Every entity and every command is reachable programmatically, with the same authorization a person gets.

IN-APP 

#### In-product assistant

Ask questions and build your own views without leaving Cordango, over the company context you already have.

SCOPE 

#### Scoped access

A key or an assistant session is bound to one user and one tenant. There is no back door that sees everything.

## AI is one way capability arrives, not the product.

Cordango uses AI to turn a description into a working capability, and that is genuinely useful. It is not what the product is. The product is a shared company foundation with capabilities on top, and generation is one of four ways a capability gets there.

The distinction matters when something goes wrong. A generated capability is an ordinary Cordango application: a readable definition, the same permissions, the same audit trail, editable by hand afterwards. It is not a black box you have to regenerate in order to change.

-   SAME A generated capability is governed exactly like a catalogue one
-   READ The result is a definition a person can read and review
-   EDIT Change it by hand later without going back through a prompt

[The four ways a capability arrives →](https://www.cordango.com/platform/)

NEXT

## Ask a question that crosses three systems.

Bring one you cannot answer today without two exports and a spreadsheet. That is the fastest way to see what one shared data plane is actually worth.

[See Cordango in action →](https://www.cordango.com/company-graph/) [The platform underneath →](https://www.cordango.com/platform/)