Pricing overview
Climatiq utilizes a usage-based pricing model, primarily centered around API credits. These credits are consumed when users make requests to the Climatiq Carbon Emissions API for calculating the carbon footprint of various activities or retrieving emissions factors. The cost structure scales with the volume of API calls, ensuring that users pay based on their actual consumption of the service. This model is common among API providers, allowing for flexibility as usage fluctuates.
The core of Climatiq's offering is its database of emissions factors and the API that facilitates their application to user-provided activity data. Each API call that successfully returns an emissions calculation or data point consumes a certain number of credits. The specific credit cost per API call can vary depending on the complexity of the request or the data accessed, though general pricing is tied to the total number of credits consumed per billing cycle.
Climatiq provides a free developer plan designed for evaluation and low-volume applications, offering a set number of API credits monthly. For higher usage, a range of paid plans are available, each bundling a larger allocation of credits and often including additional features such as dedicated support or higher rate limits. These plans are structured to accommodate individuals, startups, and larger enterprises, with pricing tiers increasing proportionally with credit allowances and included functionality, as detailed on the Climatiq pricing page.
Beyond the standard credit consumption, some advanced features or premium data access might involve different credit rates or be exclusive to higher-tier plans. Users are typically advised to monitor their credit usage through a dashboard provided by Climatiq to manage costs effectively. Understanding the credit consumption of specific API endpoints is essential for predicting and optimizing expenses.
Plans and tiers
Climatiq offers several plans structured to cater to different user needs, from individual developers to large organizations requiring extensive API access and support. All plans feature the core Climatiq API for carbon emissions calculations and access to their underlying emissions factors database.
| Plan Name | Monthly Price | Key Limits / Inclusions | Best For |
|---|---|---|---|
| Developer Plan | Free | 50,000 API credits/month, standard rate limits | Prototyping, small personal projects, initial evaluation |
| Starter Plan | $99 | 500,000 API credits/month, increased rate limits, email support | Small businesses, startups, applications with moderate usage |
| Growth Plan | Custom pricing | Higher API credit allocation (e.g., millions), priority support, enterprise features | Growing companies needing significant API access, advanced reporting |
| Enterprise Plan | Custom pricing | Volume-based API credits (e.g., tens of millions+), dedicated account manager, custom integrations, SLAs | Large enterprises, high-volume applications, comprehensive ESG reporting automation |
The Developer Plan serves as an entry point, allowing users to experiment with the API without financial commitment. The Starter Plan is the first paid tier, significantly expanding the available API credits and introducing dedicated support. As usage scales, the Growth and Enterprise Plans offer progressively larger credit allocations, enhanced support options, and features tailored for organizational use, such as custom reporting and service level agreements (SLAs).
Custom pricing for Growth and Enterprise plans typically involves direct consultation with Climatiq's sales team to align the offering with specific organizational requirements, including anticipated API call volumes, specialized data needs, and integration support. This tiered approach allows users to select a plan that matches their current operational scale and budgetary constraints, with the flexibility to upgrade as their needs evolve.
Free tier and limits
Climatiq provides a free tier known as the Developer Plan, which is designed to enable users to explore the API's capabilities, develop prototypes, and integrate carbon emissions calculations into low-volume applications. This plan is available without a recurring charge and serves as an accessible entry point for those interested in leveraging Climatiq's data and services.
The primary limit of the Developer Plan is its allocation of 50,000 API credits per month. These credits are consumed with each successful API call that performs a calculation or retrieves data. For instance, a single request to calculate the emissions for a specific activity, such as a flight or electricity consumption, would typically consume one or more credits depending on data complexity. This credit allowance is reset at the beginning of each billing cycle.
In addition to credit limits, the Developer Plan also operates under standard API rate limits, which define the maximum number of requests that can be made within a specific time frame (e.g., requests per second). These rate limits prevent abuse and ensure service stability for all users. While specific rate limit figures are subject to change, they are generally sufficient for development and testing purposes.
The free tier includes access to the full range of Climatiq's standard emissions factors and calculation methodologies. However, it may not include access to premium datasets or advanced features that are exclusive to higher-tier paid plans. Support for the Developer Plan is typically community-based or limited to general documentation, rather than dedicated technical support, as detailed in the Climatiq pricing and plans overview.
Users who exceed the 50,000 monthly credit limit on the Developer Plan will need to upgrade to a paid plan to continue making API requests. This structure encourages users to transition to a suitable paid plan once their application moves beyond initial development or requires higher operational scale. Monitoring API usage through the Climatiq dashboard is recommended to stay within the free tier's limits.
Real-world cost examples
Understanding Climatiq's credit-based pricing requires considering typical use cases and how they translate into API calls and credit consumption. While exact credit costs per call can vary based on the specific endpoint and data requested, general scenarios help illustrate potential monthly expenses.
Scenario 1: Small Business Website Widget
- Use Case: A small e-commerce website wants to display the estimated carbon footprint for shipping each order. They process approximately 1,000 orders per month.
- API Calls: 1,000 API calls for shipping emissions calculation.
- Estimated Credits: Assuming 1-2 credits per call for straightforward shipping calculations, this equates to 1,000 - 2,000 credits per month.
- Cost: This usage falls well within the Developer Plan's 50,000 free credits/month. No direct cost.
Scenario 2: Mid-sized Logistics Company for Route Optimization
- Use Case: A logistics company integrating carbon emissions into its route optimization software. They need to calculate emissions for 20,000 delivery routes per month, each involving multiple segments.
- API Calls: Each route might require several API calls (e.g., for different vehicle types, fuel consumption, and distances). Assume an average of 3 API calls per route. Total: 20,000 routes * 3 calls/route = 60,000 API calls.
- Estimated Credits: Assuming 1-2 credits per call, this totals 60,000 - 120,000 credits per month.
- Cost: This exceeds the Developer Plan. It would likely require the Starter Plan at $99/month, which includes 500,000 API credits.
Scenario 3: Large Enterprise Supply Chain Assessment
- Use Case: A global manufacturing company performing quarterly comprehensive supply chain emissions assessments across thousands of suppliers and tens of thousands of products. This involves frequent, complex API calls for various scopes (Scope 1, 2, and 3 emissions).
- API Calls: The assessment involves millions of data points and calculations. For instance, processing 500,000 distinct emissions calculations per month.
- Estimated Credits: Depending on complexity, these could be 1-5 credits per calculation. Total: 500,000 calls * 2 credits/call = 1,000,000 credits per month.
- Cost: This level of usage would require a Growth or Enterprise Plan (custom pricing). The Starter Plan's 500,000 credits would be insufficient. The specific cost would be negotiated based on volume and required features.
These examples illustrate how the volume and complexity of API calls directly influence the required plan and associated costs. Users are encouraged to utilize the Developer Plan for initial estimates and then project their likely monthly credit consumption to select the most appropriate paid tier on Climatiq's official pricing page.
How the pricing compares
Climatiq's pricing model, based on API credit consumption, aligns with a common strategy among API-first technology providers. When comparing Climatiq's approach to alternatives in the carbon accounting and environmental data space, several factors come into play, including the type of service offered, the target audience, and the overall business model.
Other environmental data providers, such as Persefoni, often focus on comprehensive SaaS platforms for enterprise-level carbon accounting and ESG reporting. These platforms typically offer end-to-end solutions, including data collection, analysis, reporting, and compliance tools. Their pricing models are frequently subscription-based, often tied to factors like the size of the organization, the number of entities being tracked, or the scope of emissions being reported. Such platforms tend to have higher entry costs but provide a broader suite of integrated features, which might include audit trails, scenario planning, and advanced analytics, as detailed in their respective pricing structures.
Another category of alternatives, like Doconomy, focuses on providing tools for financial institutions to integrate carbon impact calculations into consumer transactions. Their pricing might involve transaction-based fees, licensing agreements for their API, or bespoke enterprise contracts. While their API functionality can overlap with Climatiq's in calculating emissions for specific activities, their primary business model and integration points are often different, focusing on consumer-facing applications within the financial sector.
Patch, an API-first solution for carbon removal and offsetting, also operates on an API-based model. However, Patch's primary service is facilitating the purchase and management of carbon credits, rather than providing raw emissions factor data or calculation services. Their pricing typically involves a percentage fee on carbon credit transactions or subscription fees for access to their marketplace and API. This represents a different value proposition compared to Climatiq, which focuses on providing the underlying emissions data for calculations.
Compared to these alternatives, Climatiq's strength lies in its specialized focus on providing a developer-friendly API for direct carbon emissions calculations and access to a vast database of emissions factors. Its free Developer Plan and transparent credit-based system make it accessible for developers and smaller businesses to integrate carbon data without a large upfront investment. This model is particularly competitive for organizations that prefer to build custom solutions on top of granular emissions data rather than adopting an off-the-shelf, full-suite carbon accounting platform. Companies that frequently use other API services, such as Stripe for payments or Cloudflare for network services, might find Climatiq's API-centric approach familiar and easy to integrate into existing technical stacks.
Ultimately, the choice depends on an organization's specific needs: whether they require a foundational API for custom development, a fully integrated SaaS platform for comprehensive ESG management, or a specialized service for offsetting and removal. Climatiq positions itself as a core infrastructure provider for emissions data, with a pricing model designed for scalable API consumption.