Concierca is a scoped company operating system. Every call runs server-side as the user who owns the key, filtered to what that user may see and do. You never need to manage secrets or tenancy — the server does. Your job is to use the right tool for the intent and to stay inside the discovered surface.
Session-start sequence
Run these three calls, in order, before you act on anything:1
whoami
Confirms identity, role, and tenant, and returns the authoritative tool surface:
registry_version and available_tool_schemas — the exact tools your key may use this session.2
get_context
Returns your Operating Manual — the always-load governance + knowledge block for this workspace. Optionally pass the user’s task as
query to get context scoped to what you’re about to do. Over MCP this is pull-only: fetch it yourself, it is not pushed to you.3
guardrails_get
Returns the governance rules to honor for this workspace (what is allowed, what needs a human). Also pull-only over MCP, so fetch it at session start rather than assuming defaults.
Discover before guessing
Concierca resources are named by live, workspace-specific identifiers. Never invent them. If you need to reference any of the following, call its discovery tool first and use a value it returned:
A guessed slug, column, ID, category, or grant string is the single most common cause of a failed or wrong call. When in doubt, list first.
The compact contract
Keep this block in your working context for the session. It is the whole contract in one paragraph:Which surface for which need
A one-line map of the seven surfaces (each has its own routing detail in What are you trying to do?):- Data — exact records & numbers (products, stock, orders, prices, customers).
- Knowledge — durable company truth (SOPs, strategy, policy, brand rules).
- Memory — episodic / contextual recall (past events, user-specific facts).
- Agent Runs — what an agent did before.
- Skills — reusable AI capability.
- Missions — orchestrated, multi-step workflows.
- Vertical — market & competitive intelligence.
Registry & reconnect
whoami.registry_version and whoami.available_tool_schemas are authoritative for the tools you may call. If the server’s registry_version differs from the tool set you loaded, your client is out of date:
- Report a registry/client mismatch to the user rather than proceeding.
- Reconnect to refresh the tool list. In ChatGPT the connector loads tools only at creation time, so delete the connector and recreate it — a re-login or reload will not refresh it.
- Never invent a replacement tool name or guess at a renamed tool. If a tool you expect is absent, it is out of scope for this key or the registry moved — discover or reconnect, do not improvise.