Databases

Structured databases keep typed records together with your files. Use a database for data that an agent must query, not read. Examples are project trackers, glossaries, decision logs, and content calendars.

Schema

A database has typed properties. The supported types are text, number, boolean, date, select, multi_select, url, relation, file_reference, and asset_reference.

The keys in record values are stable property UUIDs, not property names. Thus, when you rename a property, API consumers continue to work:

{
  "values": {
    "22222222-2222-4222-8222-222222222222": "Launch",
    "33333333-3333-4333-8333-333333333333": 42,
    "44444444-4444-4444-8444-444444444444": true
  }
}

References and page bodies

• A file_reference is one file UUID. If the property allows multiple files, it is an array of UUIDs.
• An asset_reference identifies an imported binary attachment.
• A record can set contentFileId to use a normal Orcha file as its editable page body.

Referenced resources must be active and in the same workspace. Folder-scoped tokens cannot write references to resources outside their scope. Orcha redacts inaccessible references from responses.

Views, versions, and retrieval

Databases have saved table views with filters and sorting. When you update a record, Orcha merges the values and saves a version. Orcha indexes records automatically. search_context results include native record citations. These citations link to /databases/:databaseId?record=:recordId.

You can query records with search, sorting, filters, and pagination (limit up to 200). The filter operators are contains, equals, not_equals, is_empty, and is_not_empty. See the API reference and the MCP database tools.