← back to examples
core intermediate

Demand Tracker Agent

A Jido agent that tracks listing demand with boost/cool/decay actions. Demonstrates Directives — the agent's mechanism for requesting side effects like emitting domain events (Emit) and scheduling future signals (Schedule).

directives emit schedule signals state

Related guides and notebooks

Guide
Your first agent
Define typed state and run your first command.
Livebook
Your first agent
Run the companion notebook in Livebook
Concept
Actions
Understand action contracts, validation, and composition.
Next
Build your first workflow
Chain actions into a multi-step workflow.
Livebook
Build your first workflow
Run the companion notebook in Livebook
Explanation

What this example teaches

Interactive Demo

Run the agent and inspect state

Source Code

Read the production implementation

Demand Tracker Agent
id: demand-d…
50%
50
demand level (0–100)
0
Ticks
2
Schedules
—
Last Updated
Configured Schedules
*/5 * * * * → heartbeat.tick (job_id: :heartbeat)
@daily → cleanup.run (job_id: :cleanup, timezone: America/New_York)
Raw Agent State ▸ 
%Jido.Agent{
  id: "demand-demo-165282",
  name: "demand_tracker",
  description: "Tracks listing demand with scheduled maintenance",
  vsn: nil,
  category: nil,
  agent_module: AgentJido.Demos.DemandTrackerAgent,
  state: %{
    demand: 50,
    listing_id: "demo-listing",
    last_updated_at: nil,
    ticks: 0
  },
  schema: #Zoi.map<
    coerce: false,
    unrecognized_keys: :strip,
    fields: ["%{" | "}"]
  >,
  tags: []
}