Developers and agents · Planned
Give your agents facts, not scraped dashboards
If you build agents for your own business, you know the pattern: each one fetches data from each platform, the numbers disagree, and nothing limits what a given agent may touch. Selfirm plans to expose the record it keeps, already checked and attributed, through MCP and an API. None of this is available yet. This page describes the design so you can tell us what you would need.
The first tools
All of them read, or produce a proposal that waits for approval. None can move money.
| Tool | What it does |
|---|---|
get_economic_state | The state of a party within the caller’s grant: balances, holdings, what is coming due |
find_objects | Find things by kind, owner or relationship: accounts, domains, customers |
trace_transaction | Follow a movement or a figure back to its source file and row |
get_project_economics | What a product or project has earned and consumed |
simulate_capital_allocation | Try out an allocation without changing the record |
propose_business_action | Draft an action for a person to approve |
Names and shapes may change before release.
What stays fixed
An outside agent is one more executor
It appears in the same list as Selfirm’s own agents, with a grant and a log of what it did.
Out-of-scope calls are refused
Refused and recorded, not merely warned about.
Imported content is untrusted
Text inside a document is data. It cannot grant or widen a permission.
Definitions are shared
A metric means one thing, defined once, whichever agent asks.
Read next
- The permission model: what a grant contains and how a call is checked
- Yours to keep: open formats, including plain-text books
- Every number checks out: what “checked” means for the data your agent reads
Tell us what your agents need
Join the waitlist and say what you would hand to an agent first. It decides what we build first.