Overview
Cloud ERP and business management suite. Modus mines each account you select and keeps that context current.
What Modus reads
- 1Account
- 2Record Type
- 3Field
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
3context types mined
5agent tool groups
1connection method
4security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
Account list
A NetSuite account — the tenant reachable by one connection.
Record Type metadata
One NetSuite record type (`customer`, `salesorder`, `customrecord_project`) — the ERP equivalent of a table.
Field metadata
A body field on a NetSuite record type, with its declared type, enum value set, and reference target when it points at another record type.
Common use cases
- 01
Answer a finance question from the NetSuite record, in the field names the ledger uses.
- 02
Keep agents on the entities you selected.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
OAuth (managed)
Sign in through managed OAuth. Access follows the account you authorize, and the token is stored as a secret.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Metadata-first mining
Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.
Read-only by default
Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.