> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/reference/api-terminology-mapping.md).

# API Terminology Mapping

Map conceptual documentation terms to current Classic and Platform API resource names.

The [Glossary](/reference/glossary.md) defines the product terms used throughout these docs. The two API surfaces retain some different resource names. This page identifies the exceptions so you can move between conceptual guidance and implementation references without mixing Classic and Platform API terminology. Wire names and historical release terminology remain unchanged.

## API Mappings

| Conceptual Name      | API Name                             | Surface      | Description                                                                                                            |
| -------------------- | ------------------------------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------- |
| Action               | `tool`                               | Classic API  | A versioned code package that an agent can execute during a conversation.                                              |
| Call Timeline        | `timeline`                           | Platform API | Lane-based playback with actor-attributed segments on a shared timebase.                                               |
| Context Graph        | `service_hierarchical_state_machine` | Classic API  | Workflow states, transitions, guidance, and tool bindings. Platform Context Graphs have a separate resource contract.  |
| Dynamic Behavior set | `dynamic_behavior_set`               | Classic API  | A versioned set of triggers and adjustments to turn-level guidance and tool candidates; not a Platform API capability. |
| Metric Store         | `metrics`                            | Platform API | Metric definitions, assignments, and computed values; scope and eligibility follow the metric contract.                |
| Platform Function    | `function`                           | Platform API | A workspace-registered, read-only SQL, AI, Python, or table-valued computation.                                        |

Most Platform API resources - including workspaces, agents, services, sessions, skills, surfaces, triggers, and operators - use the same product name in the documentation and API. The legacy names above remain important when working with the Classic API or configuration files that originated there.

An **Agent Core** is the agent's identity and authored guidance, not a second resource or an entire deployed workflow. A **tool** is a general callable capability: Classic Actions, Platform Skills, and Platform Functions have distinct definitions and lifecycles. A **version set** selects supported component versions and preferences; it is not a workspace or an isolated environment. **Universal reasoning** and **liquid world model** describe architectural ideas, not additional API resources.

{% hint style="info" %}
The API references are definitive for current resource names and schemas. See the [Classic API](https://docs.concurrence.com/developer-guide/classic-api/core-api) and [Platform API](https://docs.concurrence.com/developer-guide/platform-api/platform-api) sections of the developer guide.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/reference/api-terminology-mapping.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.