OneOS Docs
Genesis 0.1.12 Console

Concepts

Organizations and projects

Everything in OneOS belongs to an organization. Every request acts in exactly one organization, and the gateway decides which from the credential, never from the request.

Organizations

An organization (o_…) is the boundary for resources, keys, members, usage and billing. The gateway verifies the credential on each request, attaches its organization, and services read and write only that organization's data.

  • An API key belongs to the organization it was created in, for as long as it exists.
  • A signed-in session (genesis login, the Console) acts in the organization you select. People in more than one organization switch with genesis orgs switch or the Console's organization menu.

Check which organization a credential acts in:

curl "https://os.one.ml/api/v1/whoami" -H "Authorization: Bearer $GENESIS_API_KEY"

Workspaces and projects

Inside an organization, a workspace groups projects, and a project holds resources. Some services act on a selected workspace and project rather than the whole organization:

  • Organization-wide services take the organization from the credential and need nothing more. Hives, Silos and Traces work this way; their resources carry their own ids (a Hives project prj_…, a Silos project, a Traces run).
  • Selection-bound services act inside the selected workspace and project. A signed-in session carries that selection; set it with genesis context select --organization <id> --workspace <id> --project <id>, or in the Console.

An organization API key carries no workspace or project selection. Operations that need one refuse API keys; the API reference marks them, operation by operation, from the latest test run.

One Superintelligence, Inc. · Built from Genesis 0.1.12 and the live gateway on 2026-10-20. Support