AnyDB
for LuumenAI

Read AnyDB records for context, then create and update them with approval

Connect AnyDB with an API key and Luumen can read your teams, databases, and records directly from the terminal. Look up a runbook entry, search for every record mentioning a failing service, or check who owns a change request. When something needs writing back, Luumen drafts the record change, shows it to you, and waits for approval before it lands.

The AnyDB toolbox

9 tools: 5 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadGet RecordFetch one AnyDB record by ID, including its metadata and cell content.
  • ReadList DatabasesList databases in an AnyDB team and return root and recycle-bin IDs used by record workflows.
  • ReadList RecordsReturn one page of record summaries from a database, optionally constrained by parent or template.
  • ReadList TeamsList AnyDB teams available to the connected account, including the IDs needed to discover databases.
  • ReadSearch RecordsSearch a database for records matching a keyword, with caller-controlled offset and limit.
  • WriteCopy RecordDuplicate an AnyDB record and its child-record subtree, optionally into another database or parent. Approval by default
  • WriteCreate RecordCreate a record in an AnyDB database, optionally attaching it to a parent and setting cell content. Approval by default
  • WriteDelete Record PermanentlyPermanently delete one AnyDB record. Approval by default
  • WriteUpdate RecordUpdate an AnyDB record's name, lock state, parent, user/group assignees, or cell content. Approval by default

One prompt, start to finish

What a governed AnyDB run looks like inside Luumen.

Questions

How does LuumenAI connect to AnyDB?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in AnyDB on its own?

Read actions answer immediately. Anything that writes — copy record, create record, delete record permanently, update record — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to AnyDB — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put AnyDB to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.