GLOSSARY
API / application programming interface
An API defines how programs can request functions or data from another system, including the agreed structure of requests and responses.
Integration moves work and responsibility
When a proposal application retrieves customer data from a CRM through an API, duplicate entry may disappear. A dependency also emerges: which information is current, which system is authoritative and what happens if retrieval fails? A technically successful transfer can still contain the wrong delivery address or an outdated contact. Organisational value depends on agreeing data ownership and business meaning across systems. The interface alone does not resolve those responsibilities.
Reading and writing have different consequences
Research often needs only limited read access. Changing customer records or triggering a proposal requires tighter controls, explicit permissions and handling for repeated requests. Otherwise, a retry can unintentionally create duplicate actions. MCP addresses a standard connection between AI applications, tools and data; API is the broader interface concept. Before integration, test missing permissions, timeouts and contradictory records deliberately. Observability then helps locate failures within the process. The acceptance criterion should include correct business outcomes under failure conditions, not simply a successful response during a demonstration.