AXMEAXME

AXME

Add human approval gates to any AI agent — without 200 lines of plumbing

Every approval gate requires: webhook endpoint + email service + polling loop + timeout handler + retry logic + state persistence + audit logging. Teams avoid them and agents go unsupervised.

Learn how to build production-ready human approval workflows for AI agents using AXME.

Why approval workflows block agent rollouts

Finance, legal, and operations will not let an LLM email customers, move money, or change production config without a human in the path. Engineering agrees — then discovers each approval type needs its own webhook, notification channel, timeout job, and audit export.

Teams ship agents without gates, or they ship one brittle gate and avoid the other seven patterns (review, form, clarification, override). AXME Cloud treats human tasks as durable intent states — the agent sleeps, the human acts, the workflow resumes with a tamper-evident record.

Example: quarterly board report

An agent drafts a quarterly financial summary from internal data. Before send, legal must review wording and the CFO must approve distribution. With AXME, the agent submits an intent, enters WAITING_FOR_HUMAN for legal review, then a second wait for CFO approval — each with 48-hour timeouts and escalation to a delegate.

If the agent process restarts during a three-day weekend, nothing is lost. Audit exports show who approved which version and when — not a thread in Slack.

DIY approval gate → AXME HITL

DIY (~200 lines)

# webhook + email + poll + timeout + store...

AXME

await axme.wait_for_human(task="approval", assignee=manager)

SOLUTION

How teams solve this with AXME.

Approval

Yes/no with timeout.

Review

Structured review workflow.

Form

Collect structured input.

Override

Emergency human takeover.

PATTERNS

Production details.

Escalation

Remind and reassign on timeout.

Audit trail

Compliance-ready log.

Learn more →

Implementing HITL with AXME Cloud

Wrap your agent run in axme.submit, then call wait_for_human with task type (approval, review, form, etc.), assignee, timeout, and optional escalate_to. Use delivery modes to surface tasks in your app inbox, email, or SSE dashboard.

Start with one high-risk action (external email, refunds) and expand to eight task types as patterns mature. Link every gate to /audit-trail/ exports for compliance reviewers.

Common questions

How is this different from a task queue?
Task queues move jobs; AXME intents carry lifecycle, human waits, multi-step chains, and compliance audit on one timeline.
Can approvers act from mobile?
Yes — poll or push delivery bindings let mobile clients complete human tasks without the agent process running.
What if the approver is out of office?
Configure timeout, reminders, and escalation assignees on each wait — built into the wait, not a separate cron system.

Related capabilities

Related links

Ship your first durable agent — in under 10 minutes.

Free tier. No credit card. Self-host or hosted — your choice.

Start free now Read the docs