Cloro
for LuumenAI
Structured Google and AI assistant answers, pulled on demand or queued in batches
Cloro returns structured results from Google Search and assistants like Gemini and Perplexity. Luumen reads answers, sources, supported countries, credit balance, and async queue depth directly in the terminal. When you need recurring monitoring, it queues async tasks as a previewed, approved step. Authentication uses an API key.
The Cloro toolbox
10 tools: 8 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadExtract AI AnswerSynchronously extract a Gemini or Perplexity answer for a prompt and country.
- ReadExtract Google AI Mode AnswerExtract a structured Google AI Mode answer with sources and optional rich modules for a prompt and country.
- ReadGet Async Queue StatusRead organization-wide queued and processing counts, priority distribution, and current async concurrency without modifying the queue.
- ReadGet Async TaskGet a queued Cloro task by ID, or wait with bounded polling until it reaches COMPLETED or FAILED.
- ReadGet CreditsRead the organization's current completed-charge credit balance and billing cycle.
- ReadList Supported CountriesReturn Cloro's current supported country codes, optionally filtered by provider model.
- ReadList US StatesReturn the US state and DC codes accepted for state-level targeting.
- ReadSearch GoogleExtract structured Google web or Google News results from a query and country, or web results from a complete Google Search URL.
- WriteSubmit Async TaskQueue one non-cancelable Cloro monitor task and return its task ID and estimated credit charge without waiting. Approval by default
- WriteSubmit Async Task BatchQueue 1-500 independently validated, non-cancelable Cloro monitor tasks. Approval by default
One prompt, start to finish
What a governed Cloro 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 — submit async task, submit async task batch — is shown as a plan and requires approval by default, including the 2 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 Cloro — 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 Cloro to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.