Core Concepts

Map Amigo's conceptual model to Platform and Classic resources, keeping authentication, version selection, conversations, and evidence distinct.

The two APIs use some of the same product names, but each has its own identifiers, credentials, payloads, and lifecycle rules. Use this map to find the correct implementation contract. For the relationships between data, configuration, execution, and evidence, read the conceptual Core Concepts.

Platform API

Setup

Concept	Implementation role	Continue here
Workspace	Boundary for workspace resources, data, and access; account and identity routes have their own scope	Workspaces
Agent	Versioned identity, general guidance, and communication style	Agents
Context Graph	Authored states, transitions, objectives, and state tool bindings; the service selects the graph used at runtime	Context Graphs
Skill	A companion definition with its own prompt and declared tools; the state binding governs execution and result handling	Skills
Service and version set	Deployment configuration and the selected component versions and supported preferences	Services
Channel use case and binding	Provisioned channel route connected to the service that handles it	Use Cases & Bindings

A version selection is not a separate tenant or a snapshot of all source data. Agent and Context Graph instructions guide model behavior; authorization and tool validation enforce operation boundaries.

Voice and Operations

Concept	Implementation role	Continue here
Conversation	Interaction history and lifecycle on a supported channel	Conversations
Session	Runtime context and protocol for processing an interaction; resumption and configuration loading depend on the path	Sessions
Run	Channel-neutral inventory and detail for supported execution records	Runs
Operator	An authorized person using the controls supported by the channel	Operators

Platform supports text and messaging as well as phone calls. Operator joining on the current voice path uses a phone number; browser microphone joining has been removed. Listen, takeover, handback, external transfer, and integration-write approval are distinct operations.

Data

Concept	Implementation role	Continue here
World model	Source-attributed observations, entities, and derived read views	Data & World Model
Connector	Supported source ingestion and separately controlled outbound delivery	Connector Runner
Intake	Authenticated submission to supported dataset sources	Customer Data Intake
Generated memory	Bounded observations and narrative context derived from previous interactions	Memory

Event acceptance, projection freshness, generated memory, and external delivery have different lifecycles. A recognized caller binding can locate an entity; it does not replace the verification required by the workflow.

Classic API

Setup

The Classic API scopes resources to an organization and acts through an authenticated user. A service and its selected version set determine the configured agent experience. Classic Tools, also called Actions, are versioned code packages. Dynamic Behaviors are a separate Classic feature; they are not Platform Skills or Platform triggers.

Continue with Services, Agents & Context Graphs, Tools, and Dynamic Behaviors.

Users

A Classic user has an identifier, role-based permissions, and associated context. A user model is generated or maintained context used for personalization; it is not an authoritative copy of every clinical or scheduling fact.

See Users, User Models, and Permissions.

Conversations

Classic conversation creation and interaction use incremental NDJSON event streams on their streaming paths. A conversation contains interactions and retained messages. Consumers must process the documented event variants, distinguish errors from completion, and finish or resume the conversation under the relevant lifecycle contract.

Voice-note and realtime paths have their own media and protocol rules. See Conversations, Events, and Lifecycle & Finish.

Choosing the Right Contract

Use the API named in your service configuration and integration agreement. Do not assume a shared concept name implies shared storage, automatic migration, credential compatibility, or the same event format. Terminology Mapping records the product-to-schema names; Choose Credentials explain the separate credential flows.