Skip to main content

​
Welcome to Cloro API

The Cloro API extracts structured data from ChatGPT, Perplexity, Microsoft Copilot, Google AI Mode, Google AI Overview and other AI models at scale. Get parsed markdown, sources & citations, and track what AI says about your brand across multiple regions with our unified API.

​
Key Features

Structured Data Extraction

Extract AI responses with parsed markdown and sources & citations

Monitor Endpoint

Extract structured data from ChatGPT, Perplexity, Microsoft Copilot, Google AI Mode, Google AI Overview and other AI models

​
Base URL

All API requests should be made to: 
https://api.cloro.dev

​
Authentication

All API endpoints require authentication using API keys in the Authorization header. API keys follow the format sk_live_32hexcharacters for production or sk_test_32hexcharacters for testing. 
Authorization: Bearer sk_live_32hexcharacters
The authentication scheme is defined in our OpenAPI specification: 
"security": [
  {
    "bearerAuth": []
  }
]

​
Getting Started

  1. Get your API key: Visit cloro.dev/contact to get your API key
  2. Make your first request: Try extracting structured data with our monitor endpoint
  3. Analyze results: Review parsed markdown and sources & citations from AI responses

​
Rate Limits

The Cloro API implements rate limiting to ensure fair usage and optimal performance for all users:
  • 1,000 requests per hour per API key
  • Rate limits reset every hour at the top of the hour (e.g., 2:00 PM, 3:00 PM)
  • Requests are distributed evenly across the hour to prevent bursts

​
Handling Rate Limits

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response: 
{
  "success": false,
  "error": "Rate limit exceeded. Try again in 15 minutes.",
  "retry_after": 900
}
Best Practices:
  • Monitor the X-RateLimit-Remaining header
  • Implement exponential backoff for retries
  • Cache responses when possible to reduce API calls
  • Distribute requests evenly throughout the hour

​
Pricing

Extract AI responses at scale with our flexible credit-based system. Pay only for successful data extractions, no hidden fees. View our pricing plans for more details.

​
Error Handling

The API uses conventional HTTP response codes:
  • 2xx - Success
  • 4xx - Client errors (bad request, authentication, etc.)
  • 5xx - Server errors
All error responses include a JSON body with error details: 
{
  "success": false,
  "error": "Error description",
  "details": [...] // Additional validation details when applicable
}

​
Support

Need help? We’re here to assist: