canonical: https://jentic.com/apis/positionstack.com/positionstack-api

# positionstack API

positionstack offers a powerful and free geocoding API for forward and reverse geocoding, supporting batch requests, multiple output formats, and optional data modules for timezone, sun, country, and bounding box information. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically batch forward geocoding, forward geocoding. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Batch Forward Geocoding
- Forward Geocoding
- Reverse Geocoding

## Use cases

### CRM Operations

Use the positionstack API to perform crm operations programmatically. The API provides 4 endpoints covering core functionality including batch forward geocoding, forward geocoding, batch reverse geocoding.

Example prompt: Call POST /forward to batch forward geocoding

### Automated Forward Geocoding Management

Automate forward geocoding operations by combining multiple positionstack API endpoints. Agents can forward geocoding and then batch reverse geocoding in a single workflow.

Example prompt: Call GET /forward to forward geocoding, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call positionstack API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'batch forward geocoding', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/forward` | Batch Forward Geocoding |
| GET | `/forward` | Forward Geocoding |
| POST | `/reverse` | Batch Reverse Geocoding |
| GET | `/reverse` | Reverse Geocoding |

## Key resources

- **Forward Geocoding** — Convert addresses to coordinates
- **Reverse Geocoding** — Convert coordinates to addresses

## Why Jentic

- **Setup:** Wiring the positionstack API by hand means handling its access_key query-parameter auth and appending the key to every geocoding request yourself. Through Jentic you install once, import the positionstack API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** positionstack takes its query and coordinates in query parameters and the request body, so you limit the agent to the operations it needs, such as forward or reverse geocoding. Only the operations you add are available to it.
- **Credential handling:** Your positionstack access key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'geocode an address' or 'reverse geocode coordinates', and Jentic returns the matching positionstack operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the positionstack API use?

The positionstack API uses an API key passed in the `access_key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I batch forward geocoding with the positionstack API?

Yes. Use the POST /forward endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the positionstack API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I batch forward geocoding through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'batch forward geocoding'. Jentic returns the matching positionstack API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the positionstack API have?

The positionstack API exposes 4 endpoints covering forward geocoding, reverse geocoding operations.

### Can I limit what my agent is allowed to do with the positionstack API?

Yes. Because Jentic One is self-hosted, you decide which positionstack operations your agent can reach, and only the operations you import are available to it. For example, you can grant forward geocoding (POST and GET /forward) while withholding reverse geocoding (POST and GET /reverse), or the other way round. Your rules govern which endpoints and credentials the agent may use, and the access key stays with your own instance rather than the agent context.