Documentation

Hired Hands is a managed AI-employee service. You hire agents from a catalog, hand them your policies and documents, and we build, host and monitor them. This is how the whole thing works.

The short version

You pick agents from a catalog of 15 roles. Each one is a real job — answering customer questions, chasing overdue invoices, drafting the week’s social posts — with 33 named jobs between them. You give an agent your own material once, and it works from that material rather than from anything it invented.

Everything an agent produces that a customer would see waits in a review queue until a person on your team approves it. That is not a setting; it is how the system is built.

The three ideas worth knowing

1. Agents answer from your material, not from the internet

An agent’s knowledge is the material you gave it. When it states a figure, code checks that figure against your source before the draft reaches you — a draft whose numbers can’t be traced back is withheld and recorded, never quietly published.

2. A person approves anything customer-facing

Replies, posts, emails and captured leads land in a queue. You approve, edit or dismiss each one. See Approvals & autonomy.

3. Connections are read through us, never handed over

When an agent needs a live fact — an order status, an invoice, a booking — the platform resolves your stored credential server-side, calls the provider, and strips anything credential-shaped out of the result. The model sees the answer; it never sees the key. See Connections.

Where to go next

  • The agentsEvery role you can hire, the jobs each one runs, and what runs on a schedule.
  • Approvals & autonomyNothing reaches a customer without a person approving it. How that works.
  • ConnectionsConnecting your tools, what an agent can read, and how credentials are handled.
  • Pricing & billingWhat an agent costs, how the bill changes, trials, and the guarantee.
  • API referenceAuthenticate with an API key and drive your agents from your own backend.
  • WebhooksGet a callback when an agent finishes a run or produces work to review.

How this page stays true

Every count, price and capability in these docs is read from the code that implements it, not typed here a second time — so a price change moves this page in the same commit. The prose that can’t be derived is checked weekly by one of our own agents against what we actually ship, and any drift becomes a correction for a person to approve. It is the same Knowledge Keeper you can point at your own help centre.