---
title: "Canonical verbs: one action name, every system - actionlake"
description: "A canonical verb is one standard name for the same operation across every system, such as service.ticket.create. Why agents need it and how fan-out works."
canonical: https://actionlake.com/glossary/canonical-verb
updated: 2026-10-24
---

Platform and integration

# Canonical verbs

A canonical verb is one standard name for the same operation across every system that supports it, written domain.object.operation, such as service.ticket.create, so an agent learns an action once and can run it against any connected system.

Updated 24 October 2026 Also called Canonical action name, Shared action name 2 sources checked

**On this page**

Connect an agent to every system you run.

100,000 calls free a month. No card.

[Start free](https://actionlake.com/console?start=sandbox)

## What it is

Every vendor names the same operation differently: "create ticket", "add incident", "new service request", `POST /tickets`. A canonical verb gives that operation one name in three parts: a **domain** (`service`, `finance`, `crm`), an **object** (`ticket`, `invoice`, `contact`) and an **operation** (`create`, `list`, `get`, `update`, `delete`, and others).

The idea is related to resource-oriented API design. Google's AIP-121 says a small number of standard methods (Get, List, Create, Update, Delete) provide the semantics for most common operations. Canonical verbs apply that idea across vendors instead of within one API.

## Why it matters

An agent that knows `service.ticket.create` can open a ticket in whichever help desk is connected without learning each vendor's vocabulary. It also lets a platform answer "which connected systems can do this?" and lets permissions be written once: allow `service.ticket.create`, not twenty-two vendor-specific names.

## How it works

1. Each action in each connector is tagged with a verb from a shared registry.
2. An agent searches by verb, or by plain language, to find matching actions.
3. A **write** must name the system it goes to. A **read** can be sent to every connected system that implements it at once.
4. Each action keeps its vendor's own input schema; the verb names the operation, not the fields.

## Example

`crm.contact.list` with no service named runs against every connected CRM that implements it and returns the results grouped by service. `service.ticket.create` with `service: "halopsa"` creates one ticket in HaloPSA.

## Common pitfalls

- **Same name, different inputs.** A canonical verb does not mean identical arguments; read the action's schema before calling.
- **Fanning out writes.** Creating an invoice in every connected system at once is never what anyone wants.
- **Verbs too broad to mean anything.** `do.thing` helps nobody; a verb needs an object and an operation a person recognises.

## How actionlake handles it

The actionlake registry defines 8,083 verbs. Connectors use 4,936 of them, and 3,353 are shared by two or more connectors. One name reaches many systems: `service.ticket.create` 54 connectors, `finance.invoice.list` 101, `finance.invoice.create` 74, `crm.company.list` 162 and `crm.contact.list` 177 (counted from our service files, 24 October 2026). `find_actions` filters by verb. A read verb with no service named fans out to every connected system that implements it, as one grouped run with one intent; writes are never fanned out. Keys can [allow a verb](https://actionlake.com/glossary/ai-agent-permissions) rather than a vendor action. See the [connectors](https://actionlake.com/connectors).

## Questions

**What does service.ticket.create mean?**

It is a canonical verb: the domain is service (service desk), the object is ticket and the operation is create. Any connector that can create a ticket carries it.

**Do canonical verbs force a common data model?**

No. The verb names the operation; each vendor's action keeps its own input schema. Read the schema of the action you are calling.

**Can one canonical verb run against several systems?**

A read can fan out to every connected system that implements it. A write must name one system.

## Related terms

- [Unified API vs MCP A unified API normalises many vendors in one category behind a single common schema for developers to code against, while MCP is a protocol that lets an AI model discover and call each system's own tools at run time; the two solve different problems and are often combined.](https://actionlake.com/glossary/unified-api-vs-mcp)
- [AI agent permissions AI agent permissions are the rules that decide which systems, actions and data an agent's credential may reach, and least privilege for agents means granting only the actions a task needs and enforcing that limit outside the model.](https://actionlake.com/glossary/ai-agent-permissions)
- [Cross-system join A cross-system join combines records from two or more separate systems that refer to the same real-world thing, such as one customer in an accounting ledger and a ticket desk, and returns a single combined answer.](https://actionlake.com/glossary/cross-system-join)
- [MCP tool An MCP tool is a named function that an MCP server offers to AI models, described by a name, a plain-language description and a JSON Schema for its input, and invoked with a tools/call request.](https://actionlake.com/glossary/mcp-tool)
- [Action lake An action lake is a governed layer between AI agents and business systems where every action an agent may take is defined, every action it takes is authorised and priced, and every action it took is recorded, independent of the model, framework or vendor.](https://actionlake.com/glossary/action-lake)

## Sources

1. [AIP-121: Resource-oriented design](https://google.aip.dev/121) Google API Improvement Proposals · checked 22 October 2026
2. [OpenAPI Specification](https://spec.openapis.org/oas/latest.html) OpenAPI Initiative · checked 22 October 2026

[All 30 glossary terms](https://actionlake.com/glossary)

## Connect an agent. Start free.

[Start free](https://actionlake.com/console?start=sandbox) [Read the quickstart](https://actionlake.com/docs/quickstart)

100,000 calls free every month. No card. Hard caps on every key.

---

Source: https://actionlake.com/glossary/canonical-verb
More: https://actionlake.com/llms.txt