Codereadr
for LuumenAI
Read scan data and device rosters, change scanning services as approved steps
Connect CodeREADr and Luumen can read your scanning services, validation databases, registered devices, and scan records without leaving the terminal. When a workflow needs to change — a new service for a gate, an extra question after each scan — Luumen shows the exact change first and waits for your approval before writing. Authentication is by API key.
The Codereadr toolbox
16 tools: 7 read, 9 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadConfigure CodeREADr ConnectorHelper to guide configuring the CodeREADr Connector for Google Sheets.
- ReadGenerate Scan LinkGenerates a CodeREADr scan link URI that opens the CodeREADr mobile app with a pre-filled scan value.
- ReadList Supported Barcode TypesLists barcode symbologies supported by CodeREADr for scanning.
- ReadRetrieve CodeREADr DatabasesRetrieves all validation databases configured in your CodeREADr account.
- ReadRetrieve DevicesRetrieve a list of devices registered to your CodeREADr account.
- ReadRetrieve Scan RecordsRetrieve scan records from your CodeREADr account.
- ReadRetrieve CodeREADr ServicesRetrieve configured services from your CodeREADr account.
- WriteCollect Data With QuestionsCreate and attach custom questions to a CodeREADr service for data collection after scans. Approval by default
- WriteCreate CodeREADr ServiceCreates a new CodeREADr service (barcode scanning workflow configuration). Approval by default
- WriteDelete CodeREADr DatabaseDelete a CodeREADr validation database by its ID. Approval by default
- WriteDelete DeviceDelete a device from CodeREADr. Approval by default
- WriteDelete Custom QuestionPermanently deletes one or more custom questions from your CodeREADr account. Approval by default
- WriteDelete CodeREADr ServiceDelete a CodeREADr service by its numeric ID. Approval by default
- WriteDelete CodeREADr UserDeletes an existing user account from CodeREADr. Approval by default
- WriteUpdate CodeREADr QuestionAdd answer options to an existing CodeREADr question. Approval by default
- WriteUpdate CodeREADr ServiceUpdate an existing CodeREADr service configuration. Approval by default
One prompt, start to finish
What a governed Codereadr 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 — collect data with questions, create codereadr service, delete codereadr database, delete device, and more — is shown as a plan and requires approval by default, including the 5 actions 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 Codereadr — 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
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Codereadr to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.