$ bizs find "send the new wholesale prices to our 38 customers"sales.send_price_list write · needs the owner’s OK customers*, note*
Install
One line, on macOS and Linux.
$ curl -fsSL bizs.sh/install | sh
Quickstart
Three commands from nothing to a change on the record.
1
Sign in
Opens your browser once and picks the business you work on.
$ bizs loginSigned in as ana@panaderiasur.com · business: Panadería Sur
2
Say what you want
In your own words. find answers with the operations that fit, their arguments and an example.
$ bizs find "raise the price of the 25 kg flour to 31.20"
3
Run it
Every write carries a reason, and it’s saved to the record with who and when.
$ bizs run catalog.update_price --json '{"sku":"flour-25","price":31.2}' --reason "Flour went up 6%"{"ok":true,"sku":"flour-25","price":31.2,"record":"rec_9c41"}
Examples
What a session sees: short answers, the call shape it needs, JSON out.
find answers with the call
The operation, what it’s for, its required arguments and a ready example.
$ bizs find "add a note to Ana Ruiz: she prefers WhatsApp"crm.add_note write record_id*, body* a note on a contact, organization or opportunity example: bizs run crm.add_note --json '{"record_id":"rec_8f2","body":"Prefers WhatsApp"}' --reason "Asked on the call"
find says when it isn’t sure
When a request could belong to more than one place, it says so and gives each option instead of guessing.
$ bizs find "competitors in Bariloche dropped their prices 10%"ambiguous (0.48): pick by what the request is about, or ask crm.add_note a note on a contact, organization or opportunity knowledge.add_entry a fact about the market, kept in the business’s notebook
Filtered reads
Filtering and projection happen on the server, so a long list never floods the session.
$ bizs run --reason "Flour went up 6%" --steps '[{"op":"catalog.update_price","args":{"sku":"flour-25","price":31.2}},{"op":"crm.add_note","args":{"record_id":"rec_8f2","body":"New wholesale prices from Monday"}}]'[{"step":1,"ok":true},{"step":2,"ok":true}]
JSON out, so jq works
Every answer is JSON. Pipe it.
$ bizs run sales.list_orders --grep 2026-11-17 --fields total | jq 'map(.total) | add'1240
How it works for agents
The command is shaped by what agents actually do with it, tested with real sessions before every release.
The person’s words, word for word
The guide asks the agent to pass the request to find exactly as the person said it. Rephrasing is how the wrong system gets picked.
Ambiguous means ask
If find answers ambiguous, the agent picks by what the request is about, or asks. Never a guess reported as done.
Filtered on the server
--grep, --fields and --limit run before anything reaches the session, across every page of results.
No key in the session
Inside your factory, agents hold no credential at all: the factory adds who is acting, on whose behalf, at its edge.
A reason on every write
Each change is saved with who made it, when and why, so it can be traced, undone or improved later.
Asks before what matters
Anything that costs money, goes outside the business or can’t be undone waits for the owner’s OK, from the terminal too.
Early internal tests On the same tasks, an agent used about half the input tokens and half the cost through this command line than through a plain MCP server (76k against 149k tokens). Most of the gain came from the shape of the answers, so the MCP server below offers the same shape.
Signing in
People sign in with the browser. Agents and scripts outside your factory use a token.
People
bizs login opens your browser once. You choose the business; the command remembers it.
$ bizs login
Agents and scripts
A token scoped to one business and one role, made in your factory and revocable there. Inside the factory no token is needed.
$ export BIZS_TOKEN=bz_live_…$ bizs find "open quotes this week"
Agent setup
Give your agent the short guide, as instructions, a skill or an MCP server.
AGENTS.md
The guide is short on purpose: what to run, what each common operation is for, and when to ask.
$ bizs guide >> AGENTS.md
A skill
The same guide, packaged as a skill your agent loads when it needs it.
$ bizs guide --skill > skills/bizs/SKILL.md
MCP
For platforms that prefer MCP: the same find, describe and run, served over stdio.
Print the guide for agents, as text or as a skill.
bizs find "<request>"
The operations that fit a request, with arguments and an example; ambiguous with options.
bizs describe <op>
One operation: what it’s for, its arguments and an example.
bizs run <op> [--json '<obj>'] [k=v …]
Run an operation. JSON out.
--grep <text> --fields a,b --limit n
Filter and project a read on the server.
--steps '<json>'
Several writes in one call, in order; stops at the first error.
--reason "<why>"
Required on every write; saved to the record.
bizs mcp
The same surface as an MCP server, over stdio.
Exit codes
Code
Meaning
0
Done.
1
The operation failed; the error, with the call shape, on stderr.
2
Bad usage: an unknown flag or argument.
3
Waiting for approval: the owner’s OK is needed, and the request is on their list.
4
Not signed in, or the token can’t do this.
Changelog
What changed, newest first.
v0.1
First release
login, guide, find, describe and run; filtered reads with --grep, --fields and --limit; several writes with --steps; a reason on every write; the guide as text or a skill; the same surface over MCP.