Postal Data API

@postal-data-api look up the postal code 10001 and tell me what city and coordinates it corresponds to

The postal code 10001 corresponds to New York, NY in the United States. The coordinates are approximately 40.7506° N, -73.9971° W, placing it in the heart of Manhattan. This is a concise location lookup; if you need additional administrative details like county, timezone, or elevation, I can retrieve the full metadata for this postal code.

This example demonstrates the Look Up Postal Code tool, which returns city, region, and coordinates in a single query. Each successful lookup consumes one API credit from your Postal Data API balance. Use this for quick location resolution; switch to Get Postal Code Metadata if you need country-specific administrative fields.

@postal-data-api validate these postal codes in bulk: 90210, 00000, SW1A 1AA, 75001, and let me know which ones are real

Out of the five postal codes submitted, four are valid: 90210 (Beverly Hills, CA, USA), SW1A 1AA (London, UK), and 75001 (Paris, France) all exist. The code 00000 is invalid and does not correspond to any recognized postal code. The bulk validation preserved the input order and reported per-record results. This batch consumed four API credits (one per valid lookup).

This example showcases the Validate Postal Codes in Bulk tool, which handles mixed-country batches of up to 1,000 codes synchronously. Each record in the batch consumes one query credit, so a 100-code batch costs 100 credits. The tool reports per-record failures without throwing execution errors, making it ideal for data-cleaning workflows.

@postal-data-api search for all postal codes in Portland, Oregon and summarize how many distinct ZIP codes serve that city

Portland, Oregon is served by 52 distinct ZIP codes, ranging from 97201 to 97299. The search returned all postal codes matching 'Portland' in the state of Oregon, including fuzzy-match details where applicable. The most central codes (97201–97225) cover the core urban area, while higher-numbered codes serve suburban and industrial zones. This search consumed one API credit.

This example pairs the Search Postal Codes by City tool with AI reasoning to synthesize a count and geographic summary. The tool supports fuzzy matching and requires a state name or code for US searches. Each search consumes one credit regardless of result count, making it efficient for bulk discovery. Rate limits apply per your configured plan.

When real-time postal validation beats regex at checkout

A 6-person e-commerce team ships physical goods to 12 countries and sees 8% of orders fail fulfillment because customers fat-finger postal codes at checkout. The Postal Data API's Validate Postal Code tool catches bad codes before the order hits the warehouse—no regex pattern can tell you whether "90210" exists but "90219" doesn't. The bulk endpoint handles up to 1,000 codes in one call, so if you're importing a CSV of shipping addresses, you validate the entire file synchronously and flag the bad rows before anyone prints a label. The trade-off: each validation burns one query against your API balance, so this works when order volume justifies the per-lookup cost. If you're processing 500 checkouts a day and postal errors cost you $15 in re-shipping per incident, the ROI is immediate—add this MCP to your checkout assistant and let it reject invalid codes in the flow.

Mapping sales territories when postal codes cross state lines

A 10-person SaaS sales team assigns leads by region, but their CRM only stores postal codes—no city or state fields—and manual lookups waste 20 minutes per rep per day. The Look Up Postal Code tool returns city, region, and coordinates in one call, so the team's Switchy assistant can tag every inbound lead with the correct territory owner during morning triage. The Get Postal Code Metadata tool adds timezone and county data when you need finer segmentation (useful if one rep owns "Northern California counties" and another owns "Bay Area proper"). The limitation: this MCP doesn't reverse-geocode full addresses or handle apartment numbers, so if your CRM stores street addresses without postal codes, you need a different integration. For teams that already capture postal codes at signup and just need to enrich them into routing logic, this is the fastest path from code to owner assignment.

When postal metadata routes tickets faster than IP geolocation

A 4-person support team covers three timezones and wants to route tickets to the on-shift agent without asking customers "what timezone are you in?" The Get Postal Code Metadata tool returns timezone and coordinates from a postal code, so the team's Switchy assistant can assign tickets based on the billing address already in Stripe or the shipping address in Shopify. This beats IP geolocation when customers use VPNs or corporate proxies that report the wrong region. The catch: you need a postal code in the ticket metadata—if your support form doesn't capture it, you're back to asking or guessing. The Search Postal Codes by City tool helps when a customer writes "I'm in Austin" but doesn't give you the code; it returns all matches with fuzzy-match scoring, so you pick the most populous result. If your ticket volume is under 200/day and you already collect postal codes, this MCP turns address data into routing logic without a separate geolocation service contract.