# Opencage AI integration on Definable

> OpenCage Geocoder provides a simple API for forward and reverse geocoding using open data sources.

## What this connects

OpenCage Geocoder provides a simple API for forward and reverse geocoding using open data sources.

Vendor: https://opencagedata.com

## Tools available

**7** tools available. First 7:

- `OPENCAGE_GEOCODE_FORWARD` — Forward Geocode Address — Tool to convert a human-readable address into geographic coordinates. Use when you need to retrieve latitude and longitude from an address.
- `OPENCAGE_GEOCODE_GEOJSON` — Geocode to GeoJSON — Geocode addresses or coordinates and return results in GeoJSON FeatureCollection format. Use this tool when you need: - Geographic data in standard GeoJSON format for mapping applications - Forward geocoding: convert addresses to coordinates - Reverse geocoding: convert coordinates to addresses The response includes coordinates, formatted addresses, and optional annotations like timezone, currency, and sun times for each location.
- `OPENCAGE_GEOCODE_GEOJSONP` — Geocode with JSONP — Geocode an address and return results wrapped in a JavaScript callback function (JSONP format). Use this tool when you need geocoding results that can be directly consumed by JavaScript through a callback function, typically for cross-domain AJAX requests in browser environments. The response wraps standard geocoding JSON with your specified callback function name. Example response: myCallback({"results":[{"geometry":{"lat":52.5,"lng":13.4},"formatted":"Berlin, Germany",...}],...})
- `OPENCAGE_GEOCODE_GOOGLE_V3_JSON` — Geocode Google v3 JSON — Tool to perform forward geocoding and return results in Google Geocoding API v3 compatible JSON format. Use when you need Google v3 compatible output for legacy integrations. Note: This is a legacy format that may be discontinued; using the standard JSON format is recommended.
- `OPENCAGE_GEOCODE_REVERSE` — Reverse Geocode Coordinates — Tool to convert coordinates to a human-readable address. Use when you have latitude and longitude and need a readable location.
- `OPENCAGE_GEOCODE_XML` — Geocode XML — Geocode a location query and return results in XML format. Supports both forward geocoding (address to coordinates) and reverse geocoding (coordinates to address). Use this when you need XML-formatted output instead of JSON.
- `OPENCAGE_PING_OPENCAGE` — Check API Health — Tool to check API health and connectivity. Returns 'pong' if the API is reachable. Use when you need to verify that the OpenCage API is accessible and operational.

## Auth

Auth schemes: `API_KEY`.

## How agents use Opencage

Inside a Definable workflow, Opencage is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Opencage** — the Researcher (GPT-5.5) pulls context from Opencage (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Opencage** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Opencage (create record, post message, draft email).
- **Designer / Engineer → Distributor → Opencage** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Opencage (attach file, open PR comment, post status).

The Verifier checks every Opencage call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/opencage/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt
