For Agents
Validate, geocode, reverse-geocode, and autocomplete addresses across supported countries, including UK Royal Mail PAF postcode lookup.
Use for: Validate a customer's shipping address, Geocode an address to latitude and longitude, Reverse-geocode a pair of coordinates to an address, Get address autocomplete suggestions for a search box
Not supported: Does not handle routing, turn-by-turn directions, or map tile rendering. Use for address validation, geocoding, and autocomplete suggestions only.
The Acuris Geo API validates postal addresses, geocodes addresses to coordinates, reverse-geocodes coordinates to the nearest address, and returns address autocomplete suggestions across supported countries. It includes UK Royal Mail PAF postcode lookup, batch validation of up to 200 addresses, and async jobs for larger sets. Free-tier and account-keyed endpoints both report their remaining credits so callers can track usage.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Acuris Geo 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.
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%2Facuris-geo.com%2Facuris-geo" | shStep 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%2Facuris-geo.com%2Facuris-geo" | 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.
What an agent can do with Acuris Geo API.
Validate a postal address, singly or in batches of up to 200
Geocode an address to coordinates across supported countries
Reverse-geocode coordinates to the nearest address
Return address autocomplete suggestions as a user types
Look up every address at a UK postcode via Royal Mail PAF
Submit and poll async address-validation jobs for large sets
Patterns agents use Acuris Geo API for, with concrete tasks.
★ Agent Address Validation at Checkout
A commerce agent needs to confirm a shipping address before placing an order. The Acuris Geo API validates the address and returns a standardized result, so the agent can catch typos and undeliverable addresses at checkout instead of after a failed delivery.
Validate a customer's shipping address and return the standardized form or flag it as undeliverable
Address Autocomplete for Entry
An app wants a fast address search box that suggests addresses as the user types. The Acuris Geo API returns autocomplete suggestions across supported countries, letting an agent power a type-ahead field that narrows to a valid address with each keystroke.
Return address suggestions for a partial query and resolve the chosen one to a full address
UK Postcode Address Lookup
A UK service needs every delivery point at a given postcode from Royal Mail PAF data. The Acuris Geo API lists all addresses at a UK postcode, so an agent can present the exact premises list for a postcode rather than a single approximate match.
List every address at a given UK postcode and return the matching premises
Bulk Address Cleansing
A data team has a large list of addresses to standardize and validate. The Acuris Geo API validates up to 200 addresses per request and accepts async jobs for larger sets, so an agent can submit a batch, poll the job, and retrieve a cleansed list without hitting single-record limits.
Submit a batch of addresses for validation and poll the async job until the cleansed results are ready
23 endpoints — the acuris geo api validates postal addresses, geocodes addresses to coordinates, reverse-geocodes coordinates to the nearest address, and returns address autocomplete suggestions across supported countries.
METHOD
PATH
DESCRIPTION
/validate
Validate an address
/validate/batch
Validate up to 200 addresses in one request
/geocode
Geocode an address across supported countries
/reverse
Reverse-geocode coordinates to the nearest address
/suggest
Return address autocomplete suggestions
/postcode-lookup
List every address at a UK postcode
/validate/jobs
Submit an async address-validation job
/validate
Validate an address
/validate/batch
Validate up to 200 addresses in one request
/geocode
Geocode an address across supported countries
/reverse
Reverse-geocode coordinates to the nearest address
/suggest
Return address autocomplete suggestions
/postcode-lookup
List every address at a UK postcode
/validate/jobs
Submit an async address-validation job
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Acuris Geo by hand means choosing among its header key, bearer, and legacy query-key auth and picking the right regional host. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which Acuris Geo operations your agent may call, so it can validate and geocode addresses while the account, usage, and billing operations stay out of the set unless you add them.
Credential isolation
Your Acuris Geo 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 'validate a shipping address' or 'geocode an address', and Jentic returns the matching Acuris Geo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Acuris Geo API through Jentic.
What authentication does the Acuris Geo API use?
The Acuris Geo API accepts an API key in a request header, a bearer token in the Authorization header, and a legacy key query parameter, per its OpenAPI spec. Some endpoints, such as the anonymous credit check, are open with a free tier. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I geocode an address with the Acuris Geo API?
Yes. The API geocodes an address to coordinates across supported countries, reverse-geocodes coordinates back to the nearest address, and offers country shorthand variants for the US and UK. An agent can geocode, reverse-geocode, and validate addresses from the same service.
What are the rate limits for the Acuris Geo API?
The OpenAPI spec does not state fixed rate limits, but it exposes credit-balance and usage endpoints so you can track consumption. Check the Acuris Geo documentation at https://api.acuris-geo.com/docs for the quota tied to your key and free tier.
How do I validate an address through Jentic?
Import the Acuris Geo API from the Jentic directory and give your agent an intent such as 'validate a shipping address'. Jentic returns the validate operation with its input schema, your agent submits the address and reads the standardized result, and your stored key is injected at execution time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Acuris Geo API?
Yes. Write a rule that allows only the validation, geocoding, and suggest operations, so your agent can clean and locate addresses while the account, billing, and key operations stay out of reach, and every call it makes is logged.
Is there an Acuris Geo MCP server?
You don't need an MCP server to give your agent the Acuris Geo API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, so no extra server's tool definitions sit in the agent's context.
GET STARTED