Contracts for tool-using agents

Give your agents
room to work.

Define what each agent may do alone, what needs a person, and what is off-limits. Then see how it behaves on one real workflow before you hand it more.

Discuss the pilot See an example

For engineering and platform teams with an agent already using real tools. 30-day pilot, $1,000 flat.

Illustrative workspace / Support intake Shadow mode

SAMPLE CONTRACT

Support intake agent

Proposed scope for routine work.
Customer-facing actions need a person.

Update internal ticketApproved fields onlyAgent alone

03 / Built for the people building agents

Make the boundary
part of the work.

Describe boundaries in terms your team already reviews: the workflow, the actions it calls, and who signs off.

support-intake · exampleCONCEPT

workflow: support-intake
actions:
  alone: [ticket.update]
  needs_person: [email.send]
  off_limits: [record.delete]
mode: shadow
evidence: checked separately

Concept illustration. No live connection is shown.

Give your agents
room to work.

Support intake agent

Give your agents
room to work.

Support intake agent

Update internal ticket

More than a prompt.
Clearer than a checklist.

Same agent.
Different action.

Support intake agent

Define the line.
See the work.

Define

Observe

Decide

Make the boundary
part of the work.

Start with one
real workflow.

Before you
reach out.

Give your agentsroom to work.

Support intake agent

Give your agentsroom to work.

Support intake agent

Update internal ticket

More than a prompt.Clearer than a checklist.

Same agent.Different action.

Support intake agent

Define the line.See the work.

Define

Observe

Decide

Make the boundarypart of the work.

Start with onereal workflow.

Before youreach out.

Give your agents
room to work.

Give your agents
room to work.

More than a prompt.
Clearer than a checklist.

Same agent.
Different action.

Define the line.
See the work.

Make the boundary
part of the work.

Start with one
real workflow.

Before you
reach out.