positionstack API
Browse all Positionstack APIsCRMContact ManagementapiKey4 EndpointsREST
For Agents
Programmatically batch forward geocoding, forward geocoding. Covers 4 operations with apiKey authentication.
Use for: I need to batch forward geocoding, I want to forward geocoding, Search for batch reverse geocoding, Find all reverse geocoding
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
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.
Install Jentic One Beta
Connect the positionstack API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the positionstack API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpositionstack.com%2Fpositionstack-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpositionstack.com%2Fpositionstack-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with positionstack API.
Batch Forward Geocoding
Forward Geocoding
Reverse Geocoding
Use Cases
Patterns agents use positionstack API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'batch forward geocoding', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — 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.
METHOD
PATH
DESCRIPTION
POST
/forward
Batch Forward Geocoding
GET
/forward
Forward Geocoding
POST
/reverse
Batch Reverse Geocoding
GET
/reverse
Reverse Geocoding
POST
/forward
Batch Forward Geocoding
GET
/forward
Forward Geocoding
POST
/reverse
Batch Reverse Geocoding
GET
/reverse
Reverse Geocoding
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using positionstack API through Jentic.
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.
GET STARTED