IronHeart.AI
API Pricing
Runtime 01Field proof 02Use cases 03API docsStudio
API pricing
Emotion & Event-Driven Runtime powered by IronHeart.AI
VOICE STATE / SYSTEM 02

Emotion is a state.
Not a preset.

Coordinate emotional voice state and event-driven robot behavior across long, interruptible conversations.

View Cloud API pricing
THE OPERATING PROBLEM

From model output to dependable behavior.

Most conversational stacks apply an emotion tag after the response has already been composed. The output may sound cheerful or serious, but the underlying system does not carry tension, familiarity or recovery across events.

IronHeart.AI models interaction as a stream of events and keeps voice behavior connected to the current runtime state. Tempo, micro-pauses, conversational energy and response timing can change with the situation while identity remains stable.

This matters in long exchanges, interruptions and multi-step workflows. A system that remembers its state can de-escalate, resume a task and preserve continuity instead of jumping between isolated vocal styles.

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

State before styling

Voice behavior follows dialogue and relationship state rather than a decorative one-shot tag.

02

Every input is an event

Speech, messages, intents, tool results and environmental signals enter one execution timeline.

03

Continuity across outcomes

The runtime preserves context when a user interrupts, a tool fails or the interaction changes direction.

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

Event arrives

Speech, sensor input or a system outcome updates the live timeline.

02

State evolves

Context, persona and interaction intensity are recalculated.

03

Voice moves

Timing, pauses and delivery adapt without losing voice identity.

04

Outcome persists

The next event begins from the updated state rather than a blank prompt.

BUY & DEPLOY

Start with the integration path that fits the product.

Primary buyer: Teams building social robots, companions, hospitality systems, patient-facing devices and voice-led workflows where continuity affects trust.

What to measure: Measure recovery after interruption, consistency across long sessions, appropriate escalation and de-escalation, and the absence of abrupt personality resets.

Required controls: Persona boundaries, state transitions, response pacing, interruption policy, memory permissions and event hooks.

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.

Does the system claim to feel emotions?

No. It coordinates observable voice and interaction behavior according to a governed runtime state.

Can emotional behavior be restricted?

Yes. Teams define allowed ranges, transitions and safety policies for each product role.

Can event hooks trigger external systems?

Yes. Approved hooks can connect outcomes to tools, workflows and robot actions.

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]