Continuuiti API
Integrate location intelligence into your workflows. REST APIs for geocoding, climate risk, LULC, damage estimation, and physical risk intensity.
Get access to dry run mode. We will email your key and the docs.
Available APIs
From address validation to climate risk assessment, flood damage estimation, and scenario-adjusted flood depth. All return JSON responses with detailed documentation.
Geocoder API
Convert addresses to coordinates with quality validation. Batch processing up to 5,000 locations per request.
LULC API
Land cover classification with EUDR compliance scoring. Satellite imagery, deforestation detection, protected area mapping, with biodiversity screening bundled into every report.
Climate Risk API
Physical climate risk assessment. 12 hazards, multiple scenarios (SSP2/SSP5), 30-year projections to 2050.
Climate Value at Risk API
Building-level flood damage estimation using FEMA HAZUS and JRC depth-damage curves. Batch up to 5,000 buildings per request.
Physical Risk Intensity API
Scenario-adjusted flood depth estimation. Riverine + coastal, 4 return periods, SSP2-4.5 and SSP5-8.5, batch up to 5,000 locations.
Hazard event history and carbon project screening endpoints are also available; both are covered in the full API reference.
Built for production: async jobs, batch, and a free sandbox
Every API shares the same production behaviors. Learn them once, use them across the platform.
Async jobs
LULC, climate risk, and flood depth run as jobs: submit and get a 202 with a job id, poll status, then fetch the result. Geocoding, damage estimation, and hazard history answer in a single request-response cycle.
Batch processing
Batch endpoints accept up to 5,000 locations per submission (1,000 for hazard history). Submit once, poll the batch, and retrieve every result through the export API.
Free sandbox
Send "dry_run": true on any POST endpoint for a deterministic mock response through the same flow. Free and unbilled, so you can build your integration before spending credits.
Rate limits and errors
60 requests per minute and 500 per hour per account; above that you get HTTP 429 with a Retry-After header. Every API returns the same JSON error shape.
Quick Start
1
Get Your API Key
Sign up at tools.continuuiti.com and generate your API key from the dashboard.
2
Make Your First Request
Include your API key in the X-API-Key header. Send JSON payloads to our endpoints.
3
Get JSON Response
Receive structured JSON responses with all data fields for your application.
# Geocode an address curl -X POST https://api.continuuiti.com/api/v1/geocode/ \ -H "X-API-Key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"address": "1600 Amphitheatre Parkway, Mountain View, CA"}'
import requests response = requests.post( "https://api.continuuiti.com/api/v1/geocode/", headers={"X-API-Key": "YOUR_API_KEY"}, json={"address": "1600 Amphitheatre Parkway, Mountain View, CA"}, ) print(response.json())
const response = await fetch( "https://api.continuuiti.com/api/v1/geocode/", { method: "POST", headers: { "X-API-Key": "YOUR_API_KEY", "Content-Type": "application/json", }, body: JSON.stringify({ address: "1600 Amphitheatre Parkway, Mountain View, CA", }), }, ); const data = await response.json();
For end-to-end pipeline examples (geocode → climate-risk → top hazards), see the full API documentation.
The complete Continuuiti API reference
Authentication, the async job and batch flows, sandbox mode, rate limits, and every response field, with copy-paste cURL, Python, and Node examples and worked end-to-end walkthroughs.
Technical Specifications
| Base URL | https://api.continuuiti.com/api/v1/ |
| Authentication | X-API-Key header |
| Request Format | JSON (application/json) |
| Response Format | JSON |
| Available APIs | Geocoder, LULC+, Climate Risk, Climate Value at Risk, Physical Risk Intensity |
| Rate Limits | 60 requests per minute, 500 per hour. HTTP 429 with a Retry-After header above the limit. See /docs/#rate-limits. |
| Documentation | Full API reference at /docs/. |
Behind the API: Methodology & Data
Every Continuuiti API is backed by transparent methodology and documented data sources.
Geocoding Methodology →
How addresses become coordinates: pre-validation, quality scoring, match types.
LULC Methodology →
Satellite-derived land cover classification and EUDR screening.
Climate Risk Methodology →
12 physical hazards, CMIP6 projections, composite scoring across scenarios.
Damage Estimation Methodology →
HAZUS and JRC depth-damage curves for building-level loss estimation.
Flood Depth Methodology →
Riverine and coastal flood depth with return periods and quality flags.
All Methodology + Glossary →
Full data source inventory, glossary, and platform limitations.
Questions About API Integration?
Book a call with our team to discuss your integration needs.
Frequently Asked Questions
How do I get an API key?
Sign up at tools.continuuiti.com and generate your API key from the dashboard. API access is available immediately after registration.
What authentication method do you use?
All requests require an X-API-Key header. Include your API key on every request: X-API-Key: YOUR_API_KEY. Sign up at tools.continuuiti.com to generate your key. Keys are scoped per-account and can be rotated from the dashboard.
Do you support batch processing?
Yes. Every API accepts batches in a single JSON request: up to 5,000 addresses for the Geocoder, 5,000 buildings for the Climate Value at Risk API, 5,000 locations for the LULC, Climate Risk, and Physical Risk Intensity APIs, and 1,000 locations for hazard history. Larger batches run asynchronously: submit once, poll the batch, then fetch results.
What is the Climate Value at Risk API?
The Climate Value at Risk API estimates building-level flood damage using FEMA HAZUS depth-damage curves for US buildings and JRC curves for 214 countries. It returns damage ratios, structural loss, and contents loss for any building type and flood depth.
What response format do you return?
All APIs return JSON responses with consistent structure. Each response includes the requested data, metadata, and any error information if applicable.
Where can I find full endpoint documentation?
Complete REST endpoint documentation, request/response field references, and worked code examples for all APIs are at /docs/. The single-page reference covers Geocoder, LULC+ (with biodiversity bundled), Climate Risk, Flood Depth, Damage Estimation, Hazard History, and Carbon Project Screening APIs in cURL, Python, and Node.
Do you have a sandbox or test environment?
Yes. All POST endpoints accept a dry_run: true flag that validates your request without consuming quota or running the full analysis. See /docs/#sandbox for the full sandbox pattern and what dry_run returns per API.
What error codes do you return?
Standard HTTP status codes (400, 401, 403, 404, 429, 500) with consistent JSON error shape: {error: {code, message, details}}. See /docs/#errors for the full error code catalog and per-API error reference.
Ready to Integrate?
Get your API key and start building with location intelligence.
Get access to dry run mode. We will email your key and the docs.