Cloverly

Based on the available information about Cloverly, here's my platform analysis:

```json
{
  "service_type": "platform",
  "base_url": "https://www.cloverly.com",
  "auth_method": "api_key",
  "auth_config": {
    "type": "api_key",
    "location": "header",
    "estimated": true
  },
  "endpoints": [
    {
      "path": "/api/v1/calculate",
      "method": "POST",
      "description": "Calculate carbon impact of activities",
      "estimated": true
    },
    {
      "path": "/api/v1/offsets",
      "method": "GET",
      "description": "Retrieve available offset projects",
      "estimated": true
    }
  ],
  "pricing_model": {
    "type": "freemium",
    "details": {
      "model": "api_usage_based",
      "estimated": true,
      "note": "Typical carbon API pricing includes free tier with paid usage"
    }
  },
  "rate_limits": {
    "estimated": true,
    "note": "Standard API rate limits likely apply"
  },
  "capabilities": [
    "real_time_carbon_calculation",
    "activity_impact_assessment",
    "carbon_offset_integration",
    "environmental_impact_api",
    "sustainability_analytics",
    "carbon_footprint_tracking"
  ],
  "raw_analysis": "Cloverly appears to be a carbon impact calculation API platform that enables real-time assessment of carbon-intensive activities. As a sustainability-focused service, it likely targets businesses, applications, and developers looking to integrate carbon footprint calculations and offset capabilities into their products. The platform seems designed for B2B integration, allowing companies to embed environmental impact calculations directly into their workflows, e-commerce platforms, or sustainability reporting systems. Given the real-time nature mentioned in the description, it's positioned as a developer-friendly API service rather than a standalone dashboard platform. The target audience would include sustainability-conscious businesses, environmental apps, carbon accounting platforms, and any application requiring automated carbon impact assessment. Integration capabilities likely include REST API access with JSON responses, making it suitable for web applications, mobile apps, and backend systems focused on environmental impact tracking."
}
```

2/3 tests passed

```json
{
  "overall": 73,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 6.0,
    "response_parseability": 8.5,
    "error_clarity": 6.0,
    "doc_quality": 6.0,
    "auth_simplicity": 6.0,
    "latency": 9.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "freemium_api",
    "agent_friendly": true,
    "cost_predictability": "medium",
    "notes": "Usage-based pricing typical for carbon APIs, freemium tier good for testing"
  },
  "issues": [
    "No llms.txt file - agents cannot auto-discover API capabilities",
    "Limited visibility into API documentation quality from homepage",
    "Unclear onboarding complexity for developer access"
  ],
  "recommendations": [
    "Add /llms.txt file describing carbon tracking and offset APIs for agent discovery",
    "Provide clear API documentation with usage examples and rate limits",
    "Consider simplified API key generation for agent integration",
    "Add developer-focused landing page highlighting programmatic access",
    "Document common carbon calculation use cases agents might need"
  ]
}
```