Skip to main content
These docs are written for AI agents first. Every page is plain Markdown, opens with a self-contained summary, and uses exact identifiers, values and limits. Agents can read them without a browser.

​
Machine-readable entry points

The docs root is https://docs.devias.io, and these paths are relative to it: /llms.txt is https://docs.devias.io/llms.txt. Each page also has a menu that copies it as Markdown, opens it in Claude or ChatGPT, or installs the MCP server in Cursor or VS Code. The source code is the final authority. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

​
How the pages are organised

The folder says what kind of page it is. Every page follows the same conventions.
  • The first paragraph defines the subject and stands alone.
  • A heading names its subject, so a section can be read without the text before it.
  • Exact values (types, statuses, limits, defaults, error codes) are in tables.
  • Identifiers are in code font: record_event, isRequired, devias plan.
  • A final Related list links to the pages that continue the topic.

​
Rules when acting on Devias

  1. Every id in a module is a uuid. Generate ids with devias id <count>. Never write readable or dotted ids.
  2. Run devias plan and read its output before devias apply. Never pass --allow-destructive unless a deletion is intended.
  3. devias plan and devias apply need an API key with { "module": ["manage"] }. A key created in the studio can only read records.
  4. Do not edit what a module owns. A workspace changes a module’s items by adding its own fields or by copying a workflow. An edit of an owned item is refused as a CONFLICT.
  5. A workspace id is not a uuid. Copy it from Settings → General.
  6. Use the OpenAPI document for routes and schemas instead of guessing.
  7. An agent acts with the role of the person who asked. A tool set to Ask first waits for approval, and an agent must not try to route around it.

​
Find the page for a task