Reference
Reference material for building against Okashic.
MCP tools
Agents reach the broker over MCP and call named tools. Each call is authenticated by the agent’s API key, filtered on the way out, and written to the audit log.
- Connections —
okashic.connections.listandokashic.connections.getread the connections an agent may use and each one’s operations.okashic.capability.invokeruns an operation on a connection; the broker injects the credential and returns the filtered result. - Sessions —
okashic.sessions.openandokashic.sessions.closestart and end a website session, andokashic.session.requestdrives a proxied one. - Files —
okashic.files.list,get,search,put, andupdateread and write the files an agent can see.okashic.records.createdeposits a secret or login, write-only. - Manifests —
okashic.manifests.listandokashic.manifests.findshow the connectors that exist to bind, andokashic.connection.requestasks you to connect a service the agent needs.
File and folder conventions
The wiki, scripts, and Apps live in your vault’s files. See Your assistant for what each one is, and Vault for how files and folders work, including agent-accessible folders and retention windows.
Command-line clients
okashic drives whatever broker is running and owns account and agent work; okashic-broker runs
the headless service. Run okashic --help or okashic-broker --help for the full list of commands
and their flags.