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

# API Terminology Mapping

The conceptual documentation uses product names intended for readers, while 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.

## 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  | The state machine that structures conversation flow and agent reasoning.        |
| Dynamic Behavior  | `dynamic_behavior_set`               | Classic API  | A runtime rule that modifies agent behavior when conversation conditions match. |
| Metric Store      | `metrics`                            | Platform API | Workspace-level built-in and custom quality metrics.                            |
| Platform Function | `function`                           | Platform API | A declarative SQL, AI, Python, or table-valued function that an agent can call. |

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.

{% hint style="info" %}
The API references are definitive for current resource names and schemas. See the [Classic API](https://docs.amigo.ai/developer-guide/classic-api/core-api) and [Platform API](https://docs.amigo.ai/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.amigo.ai/reference/api-terminology-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.