QuintaDB
for LuumenAI
Read QuintaDB forms and records freely, change records as approved steps
Connect QuintaDB with an API key and your team can ask about the data it already keeps there. Luumen lists forms, reads field definitions, pulls records, and searches with explicit predicates. When a record needs to be created, updated, or removed, the agent shows the field IDs and values first and waits for your approval.
The QuintaDB toolbox
12 tools: 7 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet DatabaseGet metadata and resource counts for one allowed QuintaDB database by app ID.
- ReadGet RecordGet one record by exact ID from an allowed QuintaDB database.
- ReadList FieldsList the fields in a QuintaDB form, including field IDs and types.
- ReadList FormsList forms/tables in an allowed QuintaDB database, including IDs and record counts needed for field and record operations.
- ReadList RecordsReturn one page of records from a QuintaDB form, optionally constrained to a report.
- ReadList ReportsList QuintaDB reports/views for a form.
- ReadSearch RecordsSearch records in one QuintaDB form using explicit field or system-column predicates.
- WriteCreate RecordCreate one record in a QuintaDB form using values keyed by field ID. Approval by default
- WriteCreate RecordsCreate 2-100 QuintaDB records using sequential individual API calls in input order. Approval by default
- WriteDelete Records By IDPermanently delete only the explicitly supplied QuintaDB record IDs from one form. Approval by default
- WriteUpdate RecordUpdate selected fields on one QuintaDB record using a field-ID keyed values object. Approval by default
- WriteUpdate Records By IDUpdate 2-100 exact QuintaDB record IDs using sequential individual API calls in input order. Approval by default
One prompt, start to finish
What a governed QuintaDB run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create record, create records, delete records by id, update record, and more — 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.
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.
Every call to QuintaDB — 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.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put QuintaDB to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.