API Terminology Mapping

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

The Glossary 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.

The API references are definitive for current resource names and schemas. See the Classic API and Platform API sections of the developer guide.