hurozo
First step

Set up your first agency

Create an agency, add workers, attach canon, and assign its first task.

Worker Tools

Manage worker

Tune the role and tools for this agency teammate. Graph wiring stays internal.

Tools

Loading...

Worker View

No tools selected
Team worker Untitled Agent Describe what this agent should do. HurozoAgent

Worker Chat

Describe the worker you want to add to this team, or what you want to change.
Draft JSON 
{}

Teams

Teams are managed from Agency.

Connectors

Connectors

Connect services for the current agency

Loading connectors…

Agency

Team workspace

Planning

Filters

Build

Runs

Execution activity

Runs

Inspect Worker work, tool calls, reasoning summaries, and failures.

Select a run to inspect its activity.

Files

Agency files

    Documentation

    Contact Us

    New message

    To: hi@hurozo.com

    Hurozo CLI

    Terminal-first agent work

    Hurozo CLI

    The same Hurozo agent runtime, model routes, approvals, and connected tools from your shell.

    Install with Homebrew 
    brew tap hurozo/hurozo-cli
brew install hurozo-cli

    View latest GitHub release

    Hurozo CLI running in a terminal

    Model routing

    Switch between Hurozo, Gemini, Opus, and ChatGPT-backed routes when your account is configured for them.

    Approvals

    Review tool permissions from the terminal and keep remembered decisions scoped to the exact operation.

    Second opinions

    Use model arbitration to ask another available route for critique, checks, or a different perspective.

    Connected tools

    Use the same account-backed connectors and skills available in Hurozo's desktop and WebCLI experiences.

    First run

    After installation, run hurozo. The CLI walks you through account authentication and any model-specific sign-in or secret setup that your selected route requires.

    Hurozo SDK

    Python agent invocation

    Hurozo SDK

    Invoke saved Hurozo agents from Python using the same API tokens, inputs, outputs, and runtime routing used by Agent Builder.

    Install 
    pip install hurozo
    getting_started.pyPython
    import json
import os

from hurozo import Agent

os.environ["HUROZO_API_TOKEN"] = "YOUR_API_TOKEN"
agent = Agent("sentiment-analyser")
inputs = {
    "prompt": "Analyze sentiment and return JSON. Text:",
    "input": "I am very happy!",
}

result = agent.run(inputs)
print(json.dumps(result, indent=2))

    Agent lookup

    Use an agent name, saved agent id, or agent UUID. The SDK resolves the correct execution target.

    Structured inputs

    Pass a Python dictionary matching the API input keys exposed by the saved workflow.

    Hosted runtime

    Runs against Hurozo's execution endpoint, including model routing, tools, outputs, and usage accounting.

    Token setup

    Create an API token from Account settings -> Manage API Tokens, then set it as HUROZO_API_TOKEN before running scripts.

    An accountable AI workforce

    Your customer support, run by AI you can answer for.

    Give a team of AI workers real customer work. Hurozo keeps their permissions, judgment calls, artifacts, and complete operating record in one place.

    Set up your agency See how work moves
    • Human gates for consequential actions
    • Bring your own models and connectors
    • EU-resident operating model

    A normal working day

    The queue moves. You stay in control.

    Workers pick up clear assignments, use only the capabilities you gave them, and bring decisions back to a person when the boundary says they should.

    01

    Work arrives

    A customer message, scheduled story, webhook, or teammate creates an assignment on the Team board.

    02

    The right worker takes it

    The owner sees the task, its history, canon, colleagues, tools, and the exact limits of the role.

    03

    Boundaries hold

    Read actions can run automatically. Sending, deleting, spending, or publishing can stop for approval.

    04

    The result remains

    Comments, artifacts, tool calls, decisions, and costs become one durable record you can inspect later.

    Start with the pain

    Hire the worker that fixes your Tuesday.

    Start with one useful job. Add more people, canon, and autonomy only when the work earns it.

    Support

    Morning triage

    The wall of unsorted mail, read, tagged, prioritized, and assigned before stand-up.

    Support

    First reply

    A grounded first answer with the account facts already in it, ready for review or delivery.

    Support

    Escalation spotter

    The customer about to churn, caught while a human still has a useful choice to make.

    Sales

    Prospect brief

    An hour of account research returned as a concise brief with evidence and next steps.

    Finance

    Invoice follow-up

    Overdue invoices followed up in your voice, on your schedule, within your limits.

    Knowledge

    Answer desk

    Questions answered from live company canon, with the source visible beside the answer.

    The operating system

    Everything a worker needs. Nothing it should not touch.

    The platform contract follows every worker, whether it runs inside Hurozo or connects from another agent platform through A2A.

    Permission walls

    Capabilities and actions are governed per worker. Read can be automatic while send, delete, or publish waits.

    Human judgment

    Approval requests appear in the work itself, with the exact action and arguments a person is deciding on.

    Versioned artifacts

    Reports, drafts, code, and research live in the worker repository instead of disappearing into a transcript.

    Model choice

    Use Hurozo, ChatGPT, OpenAI, Gemini, or Anthropic at the worker level while keeping one operating contract.

    Full activity

    Every tool call, state transition, approval, response, and failure is available in the run record.

    Living canon

    Connect the documents your company already maintains. Workers consult the current source instead of a copied prompt.

    Governance, staffed

    Accountability is part of the team, not a report added later.
    01

    The operator sets the brief

    Name the domain, decision rights, stop conditions, review policy, tone, and boundaries before the worker starts.

    02

    The platform enforces the limits

    Connectors keep their credentials inside Hurozo. Workers receive callable capabilities, not unrestricted secrets.

    03

    The reviewer can see the evidence

    The story contains the request, discussion, artifacts, approvals, and run activity needed to stand behind the result.

    Meet the workforce

    Build a company of roles, not a drawer of prompts.

    Give workers human names, a clear job, operating boundaries, skills, canon, tools, and a place on a real team. Talk to them directly or assign work through Team Planning.

    1Agency with its own connectors, policy, and canon
    NTeams for distinct functions, regions, or responsibilities
    24/7Scheduled and event-driven work without an open browser
    A2ALocal and remote workers under the same coordination model

    The bridge

    Ask what the team did. See the record.

    Chat and voice are the fast path into the workforce. Team Planning, repositories, and run activity remain the source of truth.

    Beatrice reviewed the morning calendardone
    Lars attached the deployment reportreview
    Clara requested approval to publishneeds you
    Martin assigned the security reviewdoing

    Start with one worker and one job worth finishing.

    Open the desktop, create an Agency, add a worker, and give the team its first assignment.

    Set up your agency Talk to Hurozo