PostGrid Verify MCP integration for AI agents.
Connect AI agents to PostGrid Verify through 4 structured actions, including lookup city state from postal, autocomplete address, and parse address. Review a…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the PostGrid Verify integration exposes
The PostGrid Verify Agent App exposes 4 provider-backed actions for location and data work. Its current contract lets an authorized agent look up city and state or province matches for a postal or zip code with postgrid verify, autocomplete a partially specified us or canadian address with optional location filters, and parse a single-line address into component fields with postgrid verify. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected PostGrid Verify account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real PostGrid Verify capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
lookup_city_state_from_postalREADLook up city and state or province matches for a postal or ZIP code with PostGrid Verify.
INPUTS: postalOrZip
autocomplete_addressREVIEWAutocomplete a partially specified US or Canadian address with optional location filters.
INPUTS: partialStreet / index / pcFilter / cityFilter / stateFilter
parse_addressREVIEWParse a single-line address into component fields with PostGrid Verify.
INPUTS: address
verify_addressREVIEWVerify and standardize a US or Canadian address with PostGrid Verify using either freeform or structured address input.
INPUTS: address / line1 / line2 / city / provinceOrState
INPUT CONTRACTS
Know what the action needs before it runs.
lookup_city_state_from_postal
postalOrZipOPTIONAL- The postal or ZIP code used for the lookup.
autocomplete_address
partialStreetREQUIRED- The partially written street address to autocomplete.
indexOPTIONAL- The optional completion result index to retrieve.
pcFilterOPTIONAL- Only return addresses within this postal or ZIP code.
cityFilterOPTIONAL- Only return addresses from this city.
stateFilterOPTIONAL- Only return addresses within this state or province.
parse_address
addressOPTIONAL- The address to parse on a single line.
verify_address
addressOPTIONAL- The freeform address written on a single line.
line1OPTIONAL- The first line of a structured address.
line2OPTIONAL- The optional second line of a structured address.
cityOPTIONAL- The city name for a structured address.
provinceOrStateOPTIONAL- The state or province code for a structured address.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Lookup City State From Postal
Look up city and state or province matches for a postal or ZIP code with PostGrid Verify. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
lookup_city_state_from_postalVerify with Autocomplete Address
Autocomplete a partially specified US or Canadian address with optional location filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
autocomplete_addressSAFETY BOUNDARY
Operate PostGrid Verify with explicit limits
- Authorize PostGrid Verify with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned PostGrid Verify data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in PostGrid Verify rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the PostGrid Verify task completed successfully.
CONNECTION MODEL
API key
PostGrid Verify API key sent with the x-api-key request header. Create or copy it from your PostGrid dashboard: https://dashboard.postgrid.com/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 3
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by PostGrid Verify.