Cloro provides structured data from Google Search and leading AI assistants, with synchronous extraction and asynchronous task APIs.
Synchronously extract a Gemini or Perplexity answer for a prompt and country. This spends credits and includes Cloro's 2-credit synchronous surcharge. Use Submit Async Task for ChatGPT or Copilot, which can exceed the synchronous execution deadline.
Extract a structured Google AI Mode answer with sources and optional rich modules for a prompt and country. This synchronous call costs at least 6 credits.
Read organization-wide queued and processing counts, priority distribution, and current async concurrency without modifying the queue.
Get a queued Cloro task by ID, or wait with bounded polling until it reaches COMPLETED or FAILED. FAILED is returned as a valid terminal record with its provider response details intact.
Read the organization's current completed-charge credit balance and billing cycle. Queued async work is not reserved, and even after a task reports a completed charge, the balance may take about 25 seconds to reflect it.
Return Cloro's current supported country codes, optionally filtered by provider model. This reports geographic support only and does not confirm that a provider monitor is operational.
Return the US state and DC codes accepted for state-level targeting. State targeting applies only to ChatGPT, Gemini, Copilot, and Perplexity and adds 2 credits.
Extract structured Google web or Google News results for a query and country. This synchronous call costs at least 5 credits; extra result pages cost 2 credits each.
Queue one non-cancelable Cloro monitor task and return its task ID and estimated credit charge without waiting. An accepted task continues after this call and spends the reported credits on completion. Use Get Async Task to retrieve it.
Queue 1-500 independently validated, non-cancelable Cloro monitor tasks. Each accepted task continues after this call and spends its reported credits on completion. Inspect summary, partial_success, and every indexed result because one response can contain both accepted and rejected items.
The Cloro integration connects your Dench AI CRM directly to Cloro, so agents can read and act on your Cloro data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
10 actions are available for agents to invoke on your behalf. Every call runs through Cloro's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Cloro and click Connect — you'll authorize access through Cloro's own sign-in flow. No API keys or code required.
Ask an agent to use Cloro in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Cloro integration connects your AI CRM to Cloro, so AI agents can work with your Cloro data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Cloro integration currently exposes 10 actions, including Extract AI Answer, Extract Google AI Mode Answer, Get Async Queue Status, Get Async Task, Get Credits, and List Supported Countries. Agents invoke them on your behalf from chat or from automations.
No. You connect Cloro from your Dench workspace using Cloro's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Cloro's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Cloro connection from your workspace settings at any time.