Agents
Agents that keep the register current, within your limits
Issue a key, connect an agent and give it the routine work: reading renewals, finding gaps and drafting changes. Anything consequential waits for a person.
- 1
Read renewals due in the next 90 days
renewals_calendar
- 2
List open findings for those vendors
tasks_list
- 3
Check for duplicate vendors
vendors_findDuplicates
- 4
Propose an owner for Fenwick Data Labs
proposals_create
- 5
Summarise what you can still act on
Approve what matters, skip what does not
Every action in the product carries a class. The class, not the agent, decides whether it runs or waits.
Read
Lists, the renewal calendar, spend and findings. An agent may read freely inside its scope.
Write
Reversible, low-impact changes such as submitting a document to the inbox. Run directly and logged.
Sensitive and irreversible
Owner, value and term changes become proposals. Deletions and outside sends are never done by an agent.
Proposal from renewal-review
Waiting for youAssign Fenwick Data Labs to Maija Meikäläinen
Rationale: the Analytics budget area holds both analytics vendors, and nobody owns this one.
Built in
Limit an agent the way you limit a person
Keys act on behalf of the person who issued them and can never see or do more than that person.
A ceiling per key
Issue read-only keys for reporting and write keys for intake. Revoke either at any time.
Scope to budget areas
A key limited to one area sees that area's vendors and nothing else.
Policy per workspace
Switch off any capability for agents, or require approval for one that would otherwise run.
Outcomes
What changes when an agent does the routine work
The review is ready before the meeting
Ask for everything renewing next quarter with its open findings, and walk in with the list.
Gaps close between reviews
An agent can work the findings queue and propose owners, terms and fixes for you to approve.
You can see what it did
The request log records each call, including refused ones, with the key and the time.
Comparison
Automation, before and after
| Topic | Before | With the register |
|---|---|---|
| Access | A shared login or an exported spreadsheet | A scoped key that you can revoke |
| Changes | Applied silently | Proposals you approve for anything consequential |
| Record | None | A request log with every call |
| Numbers | Computed by the model | Computed by the product; the agent reads them |
Related
Use it with the rest of the product
Questions
Frequently asked questions
Which agents can connect?
Any MCP client that can send an Authorization header, such as Claude Code or Cursor, and any program that can call the HTTP API.
Does the agent calculate totals or deadlines?
No. The product computes every total and deadline. An agent reads them, so its answer matches the page.
What happens to a proposal I ignore?
It expires after a set time and nothing changes. You can also reject it with a note.