Ideal Postcodes

@ideal-postcodes search for addresses matching '10 Downing Street' in London and return the top 3 results with full postal details

The search returned 3 addresses. The primary match is '10 Downing Street, Westminster, London, SW1A 2AA' (UDPRN: 23747771, coordinates: 51.5034°N, 0.1276°W). Two additional nearby addresses were found: '10A Downing Street' and '10 Downing Street, Cabinet Office'. Each result includes thoroughfare, locality, postcode, and geographic identifiers. This search consumed 3 paid lookups from your account balance.

Search is the fastest way to resolve ambiguous addresses, but every successful result consumes a paid lookup. If you're building autocomplete UI, use Find Address Suggestions first (free) then Resolve Address Suggestion (1 lookup) only when the user selects an option—this avoids burning credits on partial matches.

@ideal-postcodes validate the address '1600 Pennsylvania Avenue NW, Washington DC 20500' and tell me if it matches USPS standards

Address validated successfully with high confidence (score: 0.95). Standardized form: '1600 Pennsylvania Avenue NW, Washington, DC 20500-0003'. USPS delivery-point verification confirms this is a valid mailing address with ZIP+4 extension. The address was corrected from your input: 'Avenue' was already abbreviated correctly, and the 9-digit ZIP was appended. This validation consumed 1 paid lookup and requires the optional USPS CASS dataset enabled on your API key.

USA address validation requires the optional USPS CASS dataset—verify this is enabled in your Ideal Postcodes account settings before relying on this workflow. The confidence score helps you decide whether to accept fuzzy matches. Each validation call consumes a paid lookup regardless of match quality.

@ideal-postcodes look up postcode 'SW1A 1AA' then summarize the area demographics and suggest which addresses would be best for a retail storefront

Postcode SW1A 1AA returned 8 addresses, all in Westminster, London. Properties include 'The Treasury, 1 Horse Guards Road' and several Parliament Street addresses. This is a government and institutional district with minimal residential population—not suitable for retail storefronts. The area serves daytime office workers and tourists. For retail, consider postcodes with higher residential density and foot traffic, such as nearby SW1P (Victoria) or W1 (West End). This lookup consumed 8 paid lookups (one per address returned).

This example pairs the MCP's address data with the AI's reasoning to answer a business question the API alone can't. Be aware that postcode lookups return all addresses at that postcode—if there are 50 flats, you'll consume 50 lookups. The MCP has no demographic data; the AI inferred suitability from address names and known geography.

When real-time address validation beats manual cleanup

A 6-person SaaS team ships a new signup flow and watches 18% of UK addresses bounce in the CRM because users fat-finger postcodes or abbreviate street names. The Ideal Postcodes MCP solves this at form-time: wire the Find Address Suggestions tool to an autocomplete field, let users pick from ranked matches, then call Resolve Address Suggestion to write the canonical record straight into your database. Each lookup costs fractions of a penny, and you skip the weekly CSV cleanup ritual. The threshold: if you're onboarding fewer than 50 UK customers a month, the API key overhead probably isn't worth it—just validate postcodes with a regex and live with the typos. Above that volume, the MCP pays for itself in support-ticket reduction alone.

Why this MCP is overkill for US-only sales ops

A 12-person sales team wants to auto-route inbound leads to reps by geography. If your book of business is UK or Ireland, the Lookup Postcode and Search Addresses tools make this trivial: feed a postcode, get lat-long and administrative area, assign the rep. But the USA dataset is optional and requires separate enablement, and the Validate Address tool leans on USPS CASS—another paid add-on. If you're running a US-only motion, you're better off with a general geocoding MCP (like Google Maps) that doesn't charge per lookup and covers all 50 states out of the box. Use Ideal Postcodes when the UK is your primary market and you need the UDPRN-level precision that American tools can't match.

When search-by-text beats asking customers to re-type

A 4-person support team fields 30 tickets a day from customers who moved, changed billing addresses, or can't remember what they entered at signup. The agent copies a partial address from the ticket, pastes it into the Search Addresses tool, and gets ranked matches with confidence scores—no need to ask the customer for their postcode or make them spell out "Flat 3A" over chat. Each search is a paid lookup, so this works when your ticket volume justifies the per-query cost (ballpark: if you're doing this more than 200 times a month, it's cheaper than the labor cost of back-and-forth). Below that threshold, just ask the customer to confirm their postcode and do a free manual lookup in your CRM.