Agents · KnowOS add-on

An agent is just another user. With its own token, limits and log.

The ontology doesn't distinguish between a person and an agent: both ask for permission to read and to act. That's why agents can be connected without opening up the database.

Check this week's critical stock.

Three SKUs will fall below the minimum in less than 10 days. I've prepared two draft purchase orders; the third is waiting on the supplier's lead time.

  • Stock and consumptionERP · today
  • Supplier lead timesSupplier record · Oct
  • 2 draft ordersAgent · today
Illustrative example

What they do

Start with these. Then build the ones your process needs.

Critical stock alerts

Warns before the stockout, not after.

Which SKUs will run out of stock this month?

Seven, all from family B. Four have an order in progress; for the other three I've left a draft purchase proposal.

  • Stock and consumptionERP · today
  • 3 proposalsAgent · today

Anomalies

Orders, returns and margins that don't add up.

  • Off-list discounts
  • Returns above the average
  • Unusual orders by customer or region

Replenishment

Proposed purchase orders, always as drafts.

Reports

Scheduled and automatic, with their sources.

With approval

Nothing runs without a person who has permission.

  • Actions always as drafts
  • Approval by role
  • Writeback to the ERP via Connect and Flow

Same rules

The same permissions and audit trail as a person.

How it works

Detect, propose, approve, execute, log.

  1. 01

    Detect

    Reads stock and consumption with its token.

  2. 02

    Propose

    Draft purchase order.

  3. 03

    Approve

    A person with permission.

    Human approval
  4. 04

    Execute

    Writeback to the ERP via Connect and Flow.

  5. 05

    Log

    What, who and when.

Example · replenishment agent token

What it can and can't do.

An agent is just another user: it has its own token and logs everything.

  • Reads stock, consumption and supplier lead times.
  • Proposes purchase orders, always as drafts.
  • Doesn't see margins, sale prices or customer data.
  • Doesn't execute without approval from a person with permission.
Request an assessment

Questions about agents

Do agents act on their own?

No. They detect and propose; actions stay as drafts until a person with permission approves them.

What can an agent see?

Only what its token allows: role, rows, columns and actions. Just like a person.

Can I connect my own agents?

Yes. They connect through the same MCP server or the API, with their own token and the same log.

What comes next?

The same foundation supports assisted finance, sales and operations management. None of that can be built on scattered data: the ontology is the prerequisite.

How are they purchased?

Agents is a KnowOS add-on. It is priced per agent and by scope, after an assessment.

Show us a question that takes an afternoon today.

A 30-minute session on a real case: a historical price list, an internal procedure, a query that today ends up as a request to IT. You leave with the scope of sources and a fixed price.