AI AGENT STORE / SERVICES

WEB DATA & EXTRACTION · FOR AI AGENTS

Smarty MCP

Validate addresses against maintained reference data through MCP or REST.

Smarty supplies structured address validation and related location tools. Agents can standardize submitted addresses and inspect match evidence before preparing mail, shipping records or customer-data updates.

Your integration checklist

What you need from your owner
Create a Smarty account, obtain secret API credentials and activate licences for the APIs you need. The MCP bulk-address tool requires explicit user confirmation of its lookup count.
Authentication
The hosted endpoint https://mcp.api.smarty.com accepts Auth-Id and Auth-Token headers or HTTP Basic auth with those credentials. Tool calls use the underlying account licences; discovery alone does not establish paid API access.
Your first task
Validate a permitted sample address and inspect delivery-point codes and footnotes, including whether an apartment or suite is missing.
Billing & payment
Plans and trial allowances depend on the selected address product and lookup volume. The US address tool charges one lookup per address, including each address in a bulk request.
Agent payment support
Not verified. Programmatic usage does not establish autonomous checkout support.
Operational limits
A returned candidate is not proof of recipient identity or completed delivery. Enhanced matching can return problematic addresses; interpret validation fields. Bulk MCP calls require user_approved=true only after the user confirms the count.

ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK

Preserve uncertain address details instead of silently completing them

Editorial recommendation · Reviewed 2026-11-12

When to choose this service

Choose Smarty when an agent needs maintained postal reference data rather than merely parsing address text. Check international coverage and product licences separately.

Postal reference data and ongoing address updates are external resources. Formatting an address with code cannot establish its presence in delivery-point records.

Suggested workflow

  1. Retain the submitted address and assign an input identifier. Select the country-specific product and matching behavior.
  2. Inspect the candidate, delivery-point result and footnotes. Ask for missing unit information when it affects the intended delivery.
  3. Show material corrections before overwriting customer data. For MCP bulk work, obtain confirmation of the lookup count and preserve input-to-result mapping.

Acceptance checks before real work

  • A street match can still lack a necessary secondary unit.
  • A corrected address does not identify the person who lives there.
  • A bulk request consumes lookups for its individual addresses.

If the workflow fails

For ambiguous results, preserve the original and request the missing information. For licence errors, check the subscribed API rather than repeatedly submitting the same addresses.

Provider documentation

Explore services for adjacent needs

Continue building your toolkit