Lob MCP integration for AI agents.
Connect AI agents to Lob through 5 structured actions, including autocomplete us addresses, bulk verify international addresses, and bulk verify us addresses…
- ACTION CONTRACTS
- 5
- 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 Lob integration exposes
The Lob Agent App exposes 5 provider-backed actions for marketing and location work. Its current contract lets an authorized agent return lob us address autocomplete suggestions for a partial address, verify and standardize multiple international addresses with lob address verification, and verify and standardize multiple us addresses with lob address verification. 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 Lob account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Lob capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
autocomplete_us_addressesREVIEWReturn Lob US address autocomplete suggestions for a partial address.
INPUTS: address_prefix / city / state / zip_code / geo_ip_sort
bulk_verify_international_addressesREVIEWVerify and standardize multiple international addresses with Lob Address Verification.
INPUTS: addresses
bulk_verify_us_addressesREVIEWVerify and standardize multiple US addresses with Lob Address Verification.
INPUTS: addresses
verify_international_addressREVIEWVerify and standardize one international address with Lob Address Verification.
INPUTS: primary_line / secondary_line / city / state / postal_code
verify_us_addressREVIEWVerify and standardize one US address with Lob Address Verification.
INPUTS: primary_line / secondary_line / city / state / zip_code
INPUT CONTRACTS
Know what the action needs before it runs.
autocomplete_us_addresses
address_prefixREQUIRED- The beginning of the US address to autocomplete.
cityOPTIONAL- The city name for the address.
stateOPTIONAL- The US state or region for the address.
zip_codeOPTIONAL- The US ZIP or ZIP+4 code for the address.
geo_ip_sortOPTIONAL- Whether Lob should sort suggestions based on the request origin's IP geolocation.
bulk_verify_international_addresses
addressesOPTIONAL- The international addresses to verify.
bulk_verify_us_addresses
addressesOPTIONAL- The US addresses to verify.
verify_international_address
primary_lineREQUIRED- The primary street address line.
secondary_lineOPTIONAL- The secondary address line, such as an apartment, suite, or unit.
cityOPTIONAL- The city name for the address.
stateOPTIONAL- The US state or region for the address.
postal_codeOPTIONAL- The postal code for an international address.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Autocomplete Us Addresses
Return Lob US address autocomplete suggestions for a partial address. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
autocomplete_us_addressesVerify with Bulk Verify International Addresses
Verify and standardize multiple international addresses with Lob Address Verification. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
bulk_verify_international_addressesSAFETY BOUNDARY
Operate Lob with explicit limits
- Authorize Lob with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Lob 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 Lob rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Lob task completed successfully.
CONNECTION MODEL
API key
Lob API key used with HTTP Basic authentication. Create or view API keys in the Lob dashboard under Settings > API Keys: https://dashboard.lob.com/#/settings/api-keys.
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
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 5
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 Lob.