For Agents
Autocomplete and resolve UK addresses by postcode or UDPRN, and verify email deliverability and phone carrier status, through six read-only GET lookups.
Use for: Find the full address for a UK postcode, Check whether this email address is deliverable before I save the lead, Retrieve the address record for a stored UDPRN, I need to autocomplete a UK address the user is typing
Not supported: Does not handle non-UK address lookup, geocoding to coordinates, sending email or SMS, or bulk list uploads. Use for UK address, email, and phone validation lookups only.
The Postio API validates UK addresses, email addresses, and phone numbers from Cloudflare's edge. Address lookups run over Royal Mail PAF plus BFPO: a free single-line autocomplete returns UDPRN suggestions, and postcode or UDPRN lookups return full delivery-point records. Email checks cover syntax, typo correction through didYouMean, disposable and role-account classification, MX lookup, and an SMTP signal, while phone checks parse the number and run a live HLR lookup for the current carrier, porting, and reachability.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Postio API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpostio.co.uk%2Fpostio" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpostio.co.uk%2Fpostio" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Postio API.
Autocomplete a partly typed UK address with the free /address/search typeahead and get back udprn and suggestion pairs
List every PAF delivery point at a postcode, ordered by building number, with /address/postcode/{postcode}
Resolve a Royal Mail UDPRN to its full address record with /address/udprn/{udprn}
Check an email address for syntax, likely typos via didYouMean, disposable or role-account status, and MX records with /email/{address}
Validate a phone number and run a live HLR lookup for its current carrier, ported flag, and reachability with /phone/{number}
Confirm a key is active and warm the connection with the free /connect probe
Patterns agents use Postio API for, with concrete tasks.
★ Agent checkout address capture through Jentic
A checkout or onboarding agent connected through Jentic searches by intent for UK address lookup, gets the Postio search operation with its schema, and feeds it what the customer typed. It shows the returned suggestions, then calls the UDPRN lookup for the one the customer picks to save a clean PAF record with postcode, post town, and thoroughfare.
Call GET /address/search with q '57 wimpole street', take the first result's udprn, then call GET /address/udprn/25742215 to fetch the full address
Lead hygiene before CRM entry
Before a new lead is written to a CRM, an agent checks the email with /email/{address} and the phone number with /phone/{number}. Disposable or role-account emails and unreachable or invalid numbers are flagged, and a didYouMean suggestion lets the agent fix a mistyped domain such as gnail.com instead of dropping the lead.
Call GET /email/alice@example.com and GET /phone/+447700900123, then report deliverability, didYouMean, isDisposable, currentCarrier, and isPorted
Postcode-to-delivery-point listing
A delivery or field-service agent lists every PAF delivery point at a postcode with /address/postcode/{postcode}, ordered by building number. Postcode whitespace and case are normalised, so W1G8YW and w1g 8yw resolve to the same record, and an empty result for a withdrawn postcode is not charged.
Call GET /address/postcode/W1G8YW with max_results 20 and return each address_line_1 with its udprn
6 endpoints — the postio api validates uk addresses, email addresses, and phone numbers from cloudflare's edge.
METHOD
PATH
DESCRIPTION
/address/search
Autocomplete a UK address
/address/postcode/{postcode}
List addresses at a postcode
/address/udprn/{udprn}
Look up an address by UDPRN
/email/{address}
Validate an email address
/phone/{number}
Validate a phone number with HLR lookup
/connect
Key and health probe
/address/search
Autocomplete a UK address
/address/postcode/{postcode}
List addresses at a postcode
/address/udprn/{udprn}
Look up an address by UDPRN
/email/{address}
Validate an email address
/phone/{number}
Validate a phone number with HLR lookup
/connect
Key and health probe
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Postio by hand means sending its pk_ key in the x-api-key header, keeping per-service keys straight, and handling 429 back-off and 402 out-of-credit responses yourself. Through Jentic you install once, import the Postio API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Postio puts the postcode, UDPRN, email, or phone number in the URL path, but those are lookup inputs rather than account resources, so rules here bound which lookups your agent may call. You choose the operations it may run, so billable email and HLR phone checks are not included unless you add them.
Credential isolation
Your Postio API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'autocomplete a UK address' or 'check if an email is deliverable', and Jentic returns the matching Postio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Postio API through Jentic.
What authentication does the Postio API use?
Per its OpenAPI spec, the Postio API takes an API key in the x-api-key header, in the format pk_ followed by the key. Postio keys are scoped per service (address, email, or phone) and can be locked to origins or IP ranges in the Postio dashboard. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
What are the rate limits for the Postio API?
The spec states that each key is limited to 30 requests per second, and bursts past that return a 429 response, so back off and retry. Postio invites you to contact it through postio.co.uk if you need higher throughput.
Is the Postio API free?
Partly. Per the spec, /connect and /address/search are free, and the other lookups are billable only on a hit with results: a postcode with no delivery points or a UDPRN that returns 404 is not charged. New accounts get their first 100 lookups free with no card needed.
Can I check whether a phone number is reachable with the Postio API?
Yes. GET /phone/{number} accepts E.164, international, or national formats, and on a valid parse runs a live HLR lookup that returns currentCarrier, originalCarrier, isPorted, and a reachability flag alongside the formatted number.
Is there a Postio MCP server?
You don't need an MCP server to give your agent the Postio API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are found by intent when needed, so no extra tool definitions sit in your agent's context.
How do I look up a UK address by postcode through Jentic?
Install Jentic One, add the Postio API from the directory, and store your pk_ key. Your agent then searches for 'list addresses at a UK postcode', gets GET /address/postcode/{postcode} with its schema, and calls it with the postcode. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Postio API?
Yes. Write a rule that allows only the free GET /address/search and the GET /address/udprn/{udprn} lookup, so the agent can capture addresses but cannot spend credit on email or HLR phone checks, and every call it makes is logged.
GET STARTED