Botster
for LuumenAI
Check Botster bots, credits, and run results, then launch or archive with approval
Connect Botster with an API key and your team can ask about scraping work in plain language. Read the credit balance, search available bots, price a launch before it runs, check job status, and pull run results as structured JSON. Launches, restarts, archives, and deletions are previewed and held for approval by default.
The Botster toolbox
11 tools: 6 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadCalculate Bot CostCalculate the credit price of one intended bot launch using the same input and bot-specific options, without launching the bot or spending credits.
- ReadGet Credit BalanceReturn the connected Botster account's available credit balance; use this before launching or restarting credit-consuming work.
- ReadGet JobGet one job's status and data-run identifiers required to retrieve run results.
- ReadGet Run ResultsReturn the complete bot-specific JSON for one data run identified from GET_JOB in the results field.
- ReadList BotsList or search bots available to the connected account and return their identifiers for cost calculation and launch.
- ReadList JobsList jobs belonging to the connected Botster account and return job identifiers for inspection or lifecycle actions.
- WriteDelete JobPermanently delete one Botster job. Approval by default
- WriteDelete RunPermanently delete one Botster data run and its stored results without deleting the entire job. Approval by default
- WriteLaunch BotLaunch a Botster bot, creating external work that may spend account credits. Approval by default
- WriteRestart JobRestart an existing Botster job, creating renewed external work that may repeat the bot's effects and spend additional account credits. Approval by default
- WriteSet Job ArchivedArchive a Botster job or restore it from the archive by setting its desired archived state. Approval by default
One prompt, start to finish
What a governed Botster 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.
This connection exposes write actions such as delete job, delete run, launch bot, restart job, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Botster — 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 Botster to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.