Agent access & documentation

Agents use their own credentials and the same event and role rules as people.

Connect an agent

1. An administrator adds the agent in Staff & agents and selects its role and event assignments.
2. Issue an individual credential and store it privately in the agent’s connection settings.
3. Use the API with a Bearer credential, or connect an MCP client to /api/mcp using Streamable HTTP.

Shared business operations

Inventory, Panel templates and Accounting work without an event. Read the studio without an event ID. For stock or saved templates, omit eventId; for general accounting, omit entry.eventId or leave it empty. Event panel copies and event operations still require an event. The same rules apply to REST and MCP. Browser agents can use read_sensory_workspace_status independently of read_sensory_event_status.

Interesting facts

Administrators create, edit and archive facts in Interesting facts, with optional inventory and sensory language links. Hosts select facts per event and use Show to group. REST and MCP share saveFact, selectFacts and screen (kind: fact, factId) actions. The public event API returns only the currently displayed active fact.

Operational rules

Practice and live records are separate. Simulations belong only in practice. Real participant corrections preserve attribution and history. Agent financial and deletion actions need human review; access changes need a human administrator.

Payments and email

Payments are recorded manually. Future processors can be connected through a common provider interface. Staff sign-in emails, Google sign-in and participant review emails appear when their business accounts are configured.