IronHeart.AI
API Pricing
Runtime 01Field proof 02Use cases 03API docsStudio
API pricing
Conversational Agents powered by IronHeart.AI
USE CASE / 02

Stateful Conversational Agent
built as infrastructure.

Deploy stateful conversational agents with realtime voice, governed knowledge, persistent memory and action orchestration.

View Cloud API pricing
THE OPERATING PROBLEM

From model output to dependable behavior.

A production conversational agent needs continuity, tool boundaries and recovery when users interrupt or change direction. Prompt quality alone does not provide an operating lifecycle.

IronHeart combines live voice, knowledge retrieval, memory policy and event-driven execution behind a configurable agent identity.

Teams can begin with a managed Cloud API pilot, move interaction-critical paths to the edge, or scope a private deployment. The partner owns the customer experience and operational policy; IronHeart supplies the cognitive runtime beneath it.

What IronHeart sells

A configurable cognitive runtime—not a one-size-fits-all robot personality. Partners purchase managed Cloud API access or scope edge, offline, private-cloud and OEM production licensing with integration support.

01

Interruptible voice

Coordinate this capability with live identity, interaction state and product policy instead of treating it as an isolated feature.

02

Governed knowledge

Configure behavior per role and environment, then preserve it through versioned testing and publication.

03

Tool orchestration

Connect the module to approved knowledge, memory and actions while retaining a clear human escalation path.

THE COMPLETE COGNITIVE LOOP

Six modules.
One interaction state.

A useful embodied system cannot treat voice, memory and action as unrelated calls. IronHeart coordinates the modules around the live person, environment, role and task.

Each module can be configured per robot or product while published versions preserve a reproducible operational state.

01Perception
02Realtime voice
03Persistent memory
04Personality
05Gaze
06Actions
01

Receive an interaction

Capture the live user, environment and task context.

02

Ground with context

Relate the current event to identity, memory and approved knowledge.

03

Select a governed response

Coordinate voice, personality, attention and policy.

04

Complete or escalate

Complete the bounded outcome or transfer with context.

BUY & DEPLOY

Start with the integration path that fits the product.

Primary buyer: Product teams and integrators building customer-facing voice and multimodal agents.

What to measure: Evaluate end-to-end task completion, conversational recovery, policy compliance and the quality of human handoff for conversational agents.

Required controls: Test refusal, escalation, memory consent, source grounding and recovery after tool failure.

01 / MANAGED

Cloud API

Prototype and launch with managed realtime runtime services and the published API plans.

Review pricing →
03 / CONTROLLED

Private Cloud

Run inside customer-controlled infrastructure with an enterprise integration agreement.

Request enterprise scope →
Foundation model forSocial interaction across perception, voice, memory, personality, gaze and actions.
Partner retainsHardware, customer experience, business rules, data policy, safety authority and go-to-market.
IronHeart providesRuntime configuration, cognitive modules, adapter contract, versioned publication and deployment support.
Commercial pathCloud API subscription for evaluation; custom scope for edge, offline, private cloud and OEM production.
FAQ

Questions before integration.

Is IronHeart.AI a complete conversational agents application?

It is cognitive runtime infrastructure. The partner owns the interface, hardware, business rules, customer relationship and go-to-market.

How can a team purchase it?

Start with a Cloud API plan for evaluation. Edge, offline, private-cloud and OEM production licensing are scoped through an integration workshop.

Can the runtime use our existing knowledge and systems?

Yes. Server-side adapters can connect approved knowledge, identity, workflow and hardware systems.

What should be validated before production?

Test refusal, escalation, memory consent, source grounding and recovery after tool failure.

BUILD WITH IRONHEART

What should your robot become?

Tell us about the embodiment, use case and deployment constraints. We will map the fastest evaluation path.

[email protected]