Centra
AvailableReact widgets for Centra's headless checkout. ISO-3 country codes, flat address fields, Next.js sample. Designed for fashion brands running Centra.
Integration guide →Integrations
Drop-in address validation for your stack.
Acuris ships open-source connectors, plugins, and SDKs for the platforms you already run — including a first-class AI-agent integration: a one-install Acuris skill for Claude, Cursor and agentic IDEs.
NEW · EXCEL ADD-IN
Address validation where your data already lives: inside Excel.
Select your columns, click Cleanse, and watch verified, standardized, geocoded addresses fill the sheet — 240+ countries, UK via Royal Mail PAF, plus email & phone cleansing. No formulas, no IT project. Works in Excel on the web, Windows and Mac.
Explore the Excel add-in →
Install in 2 minutes · 1,000 free credits, no account
NEW · MCP SERVER · FOR AI AGENTS
Your AI agent can validate addresses directly — via MCP.
Connect Claude, Cursor, ChatGPT or any MCP client to api.acuris-geo.com/mcp and it gets live tools: validate, geocode, expand UK postcodes, pull free US/Canada census enrichment — billed on your own API key, failed lookups refunded.
Connect your agent →
Hosted endpoint · agents can self-provision a free trial key
Pick your platform
Integrations for every stack
Each "Available" card ships a runnable demo so you can verify the integration before committing engineering time. "Coming" cards have a date and a notify-me CTA — we ship in the order customers ask.
Composable commerce is our home turf. Drop-in React connectors for Centra, commercetools and SCAYLE — each with a runnable demo so you can verify the integration before committing engineering time.
commercetools
AvailableTwo packages: React widgets plus a server-side API Extension handler so Cart updates are gated end-to-end. ISO-2 country codes, split streetName / streetNumber.
SCAYLE
AvailableReact widgets plus a Node handler that implements SCAYLE's first-class address-check gateway protocol. Drop-in replacement for the built-in Google Maps Autocomplete.
Integration guide →Shopify
Coming Q3 2026Embedded Shopify app for the Shopify App Store. Cart-page validation for any theme; Plus-only Checkout UI Extension for the Shopify Plus tier. Hydrogen sample included.
Notify me →WooCommerce
Coming Q3 2026Built into our forthcoming WordPress autocomplete plugin (one plugin, every WP form). Drop-in for the WooCommerce checkout block and classic shortcode checkout.
Notify me →
One plugin, every form. Other providers ship a separate package per form builder. Our forthcoming WordPress plugin hooks Gravity Forms, WooCommerce, Contact Form 7 and Elementor forms from a single install — and surfaces a shared data-acuris-autocomplete attribute for everything else.
Acuris Address Autocomplete for WordPress
Coming Q3 2026A single WordPress plugin that auto-detects and hooks the form builders you use:
- Gravity Forms — drop the Acuris field type onto any form.
- WooCommerce — billing & shipping checkout fields.
- Contact Form 7 — shortcode tag.
- Elementor — Elementor Forms address field.
- Anything else — drop
data-acuris-autocomplete="postcode"on any <input>.
Native packages submitted to each platform's marketplace, with security review handled.
Salesforce
Coming Q3 2026AppExchange-listed package. Address validation on Lead, Account, Contact, and any custom object with an Address field. Lightning Flow action included.
Notify me →HubSpot
Coming Q4 2026HubSpot Marketplace app — autocomplete in HubSpot Forms, validation workflow action, and a CRM card with cleansed addresses on every contact / company.
Notify me →Microsoft Dynamics 365
Coming Q4 2026Dynamics 365 Sales / Customer Service extension. Power Automate connector for use anywhere in the Power Platform.
Notify me →Address validation as a first-class agent tool. If your team builds with Claude, Cursor, or any other agentic IDE, Acuris ships installable skills — validate, geocode, reverse-geocode and autocomplete — that drop straight into your agent's toolbelt.
Claude Code plugin
AvailableTwo installable skills: acuris-address (validate, geocode, reverse-geocode, autocomplete) and acuris-eudi (EUDI Wallet Verifier). Install with one slash command.
Cursor rules
AvailableDrop-in .cursor/rules/ files that teach Cursor about Acuris endpoints, response shapes, country codes and common validation patterns. Updated with each API change.
Open Agent Skill
AvailableOne npx skills add away on Claude Code, Cursor, Copilot, Codex and ~30 other agentic editors via agentskills.io. Same knowledge base as the Claude Code plugin.
MCP server
AvailableA first-class Model Context Protocol server exposing validate_address, postcode_lookup, geocode, and reverse_geocode tools. npx @acuris-geo/mcp-server on Claude Desktop, Claude Code, or any MCP-aware client.
Use Acuris from any workflow tool. One integration → thousands of downstream apps.
Zapier
Coming Q3 2026Four actions: Validate Address, Lookup UK Postcode, Geocode, Reverse Geocode. Use Acuris from any of the 5,000+ apps in the Zapier ecosystem.
Notify me →n8n
Coming Q4 2026Acuris community node for n8n — the EU open-source Zapier alternative. Same four actions as the Zapier integration. Self-hostable.
Notify me →How it works
Three steps. Same shape for every platform.
01
Install the packages
Each connector is a published npm package. No private registry, no auth dance.
npm install @acuris-geo/<platform>-checkout
02
Add the proxy routes
Two thin API routes on your own backend forward to api.acuris-geo.com
with the API key attached server-side. We provide working snippets for every platform.
03
Drop the component into checkout
<AcurisAddressInput> in your address step. It emits
platform-native address shapes — hand the result straight to your
cart mutation, no boilerplate.
No connector needed
Direct API & SDKs
Every connector above is a thin layer over the same REST API. If your stack isn't listed — or you'd rather integrate directly — the official SDKs cover validation, geocoding, UK postcode lookup and email verification.
TypeScript / Node SDK
Available@acuris-geo/av-sdk — typed request/response shapes, typed error hierarchy, automatic retries on 5xx / 429 / timeouts. Zero runtime dependencies. Works in Node 18+ and edge runtimes.
Python SDK
Availableacuris-geo on PyPI — the same four endpoints plus UK postcode lookup and email verification, for backends, data pipelines and notebooks. pip install acuris-geo.
FAQ
Questions we hear often
Why are the connectors open-source?
Three reasons. (1) Trust — buyers can read the code before they depend on it. (2) Discoverability — npm + GitHub is where commerce developers actually look for integrations. (3) Pace — community PRs ship fixes faster than a private SDK does. The connectors are MIT, the underlying address-validation API is paid.
Where does the Acuris API key live?
On your backend, never in the browser. Every
connector ships React components that call your proxy
endpoints (two thin API routes), which forward to
api.acuris-geo.com with the key attached server-side.
The packages refuse to even instantiate without that boundary in
place. See each connector's architecture doc for the full picture.
What does "240+ country coverage" mean in practice?
Acuris ships address-level data for every UN-recognised country plus territories and special administrative regions. Quality varies — every country is graded by the maximum precision it supports, the same way Loqate, Precisely and HERE grade coverage: 73 reach point-coordinate geocoding — a coordinate for the individual address, either a rooftop point or the property's arrival point — most of the rest street-level or better, and the long tail is locality-centroid. See the coverage matrix for per-country tier.
How are the connectors versioned?
Each connector starts at 0.1.0 (beta — minor versions
may include breaking changes). We bump in lockstep with the
underlying SDK and ship a codemod where the migration isn't obvious.
Once a connector is in production with ≥3 reference customers we
cut 1.0.0 and adopt strict semver.
We use a platform not on the roadmap. Can you add it?
Yes. Email support@acuris-geo.com with the platform name, monthly order volume, and the integration surface you'd want (storefront widget? server-side gate? both?). We respond within two working days and add a roadmap card once we have enough signal to commit.