Cloro
10 operations0 webhooks
Cloro plugin for Corsair
Supported operations
- ChatgptWrite
Ask ChatGPT a prompt as a user in a given country and get the structured answer, sources, and shopping cards
- CopilotWrite
Ask Microsoft Copilot a prompt in a given country and get the structured answer and sources
- GeminiWrite
Ask Google Gemini a prompt in a given country and get the structured answer and sources
- Google Ai ModeWrite
Ask Google AI Mode a prompt and get the structured answer, sources, places, and products
- Google NewsWrite
Run a Google News search (1-10 pages) and get articles
- Google SearchWrite
Run a Google search (1-10 pages) and get organic results, ads, People Also Ask, and the AI Overview
- PerplexityWrite
Ask Perplexity a prompt in a given country and get the structured answer and sources
FAQ
Install corsair and @corsair-dev/cloro, add the Cloro plugin, and connect with an API key. Then call methods like corsair.cloro.api.monitor.chatgpt() from your app. Corsair syncs data per tenant.
Yes. Cloro requires an API key from your Cloro account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Cloro, GitHub, Notion, Stripe, and the rest. Trigger Cloro from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for cloro plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Cloro APIs from your backend. Local DB entities let you query synced Cloro records without hitting the API on every read.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Cloro API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/cloro in the open repo. When Cloro ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Cloro data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Cloro data on your behalf.