What Hence Assistant can do

Private beta. Running errands is limited to a single-operator internal pilot — one internal account, enabled by hand, admitted by invitation rather than by self-serve signup; anyone else gets a structured refusal instead of a run. Screenshots a step takes are stored unredacted, encrypted at rest, for 30 days. Nothing on this page is a promise that this errand runs for your account today.

Find the rate on every debt I have

The rate, balance and minimum on every debt you owe.

Move my old 401(k) into my new employer's plan

Retirement money from an old job into the plan at your new one.

Capture my full 401(k) or 403(b) match

The contribution rate that captures every dollar your employer will match.

Ask for a lower interest rate

A lower purchase APR on a card in good standing.

Get my overdraft fees back

A refund of the overdraft and returned-payment fees on a checking account.

Each card’s own page carries that errand’s published ceiling, which is generated rather than written here: a ceiling stated twice is a ceiling that can drift.

One page per errand family

An errand family is a group of errands that share a shape — reading the terms of the debts you carry, getting the most out of an employer retirement plan, asking a counterparty to change something. Each family gets one page in this section. Every family page carries the same seven things, for every errand in it:

Field	What it tells you
Intents	The ways of asking that reach this errand.
Admission	The conditions that make the errand the wrong tool, and therefore the reasons it can refuse.
Required inputs	What it needs from you, and what it will take from your profile instead of asking.
Published ceiling	The furthest outcome state it may reach — DONE, READY, GUIDED or REFUSED, plus the conditional state a named condition unlocks. Enforced in the runtime, not advisory.
Blockers and instruments	What can stop it, and any licence or credential it would need but does not hold.
Jurisdiction	Where the errand’s rules apply. The first errands are US-only.
Freshness	When the underlying procedure was last verified.

The ceiling is the field to read first. It is the difference between “this will be done” and “this will be brought to the last step and handed to you”, and it is published before you delegate rather than discovered afterwards.

These pages are generated, and never hand-edited

The family pages are emitted from the capabilities manifest — the same generated record the connector serves to your assistant over MCP, produced by the same generator that emits the instructions the runtime follows. One fact, one source. That is what makes a published ceiling worth anything. If a page were written by hand it could say READY while the runtime allowed something else. Because the page, the manifest and the runtime’s instructions come out of one generator, a ceiling that moves moves everywhere at once — and shows up in the changelog.

The contract the generator emits into

Recorded here so that a page appearing in this section can be checked against it:

Source of truth — the capabilities manifest, built from the errand corpus at a pinned commit.
Output — one MDX file per family under capabilities/, with title and description front-matter, a plain-English account of what the errand does and what it asks you to approve, and then the seven fields above, in that order.
Navigation — each generated page is added to the “What Hence Assistant can do” group in the site config.
Committed, not built here — generated pages are committed to the repository like any other source. A regenerate over an unchanged corpus is byte-identical, so the diff after regenerating is what keeps them honest.
Never hand-edited. A correction belongs in the corpus or the generator; an edit made here is overwritten and, worse, is invisible until it is.

Where the ceilings are summarised

The five errands and their ceilings are also listed side by side on What Hence Assistant executes. The family pages above are the longer form, and they are the generated ones.

Start here

Connect

How tasks work