Give Claude, Cursor, Windsurf, and custom agents secure access to verified address lookup, validation, barcode, and web extraction APIs — through MCP or direct REST from one platform.
8+
Production APIs
2
Access Methods
99.9%
Uptime SLA
Agent Infrastructure — two access patterns, one platform
Your AI Agent
Claude · Cursor · Windsurf · Custom
▼ MCP Protocol / REST API
APITier MCP Server
Subscription-gated tool access
▼ MCP Protocol / REST API
Production APIs
Address · Email · VAT · Barcode · Web
CAPABILITIES
Give your agents access to Royal Mail PAF, HMRC, and other authoritative sources. Every result is grounded — no hallucinated addresses, phone numbers, or VAT records.
The same production APIs serve your backend applications and your MCP-connected AI agents from a single APITier account — one key management interface, one billing plan.
Only the APIs you subscribe to are exposed to your agent. Unsubscribed tools are invisible through MCP, keeping your agent environment aligned with your active plans and budget.
Use MCP for agent-native tool calls and the REST endpoints for backend integrations — both access the same production APIs, the same data, and the same SLA guarantees.
Every API is hosted on AWS EU-West-1 with a 99.9% uptime SLA and sub-2 second response times at the 95th percentile. No development-tier limitations on live agent calls.
Separate API keys and MCP keys let you grant AI clients only the access they need. Rotate, revoke, or scope keys per environment without affecting your application integrations.
USE CASES
Production APIs that power the verification and data workflows AI agents run most often.
Support agents handling inbound tickets can validate the customer's address, email, and phone number against authoritative sources before updating a CRM or triggering a fulfilment action. No manual lookup, no guessed data.
Validate delivery address before raising a re-send or refund
Verify customer email is deliverable before sending follow-up
Check phone number format and carrier for SMS routing
Detect mismatched address and IP country as a fraud signal
HOW TO START
Explore the API catalogue and subscribe to the production APIs your agents and applications will use. Every account gets 20 free requests — no card required to start.
Browse API CatalogueCreate an API key for direct REST integrations and an MCP key for agent clients. Both are available from your APITier account dashboard instantly after sign-up.
Add the MCP config to Claude, Cursor, or Windsurf for agent tool access. Use the REST endpoints and API key for your backend applications. Both run on the same production APIs.
NEXT STEPS
See how APITier exposes subscribed APIs as MCP tools for Claude, Cursor, Windsurf, and custom MCP clients.
View MCP ServerBrowse the full set of production APIs available for address lookup, validation, conversion, and barcode automation.
Browse CatalogueExplore a concrete AI-agent workflow with live UK address validation, enrichment, and fraud signal detection.
Explore Use CaseFAQ
What is APITier AI Agent Infrastructure?
APITier is a production API platform that connects AI agents — running in Claude, Cursor, Windsurf, or custom frameworks — to authoritative data sources through MCP and direct REST APIs. It gives agents access to verified address, validation, barcode, and web extraction tools without hallucination risk.
How do AI agents access APITier APIs?
Through two channels: MCP for agent-native tool calls (add a JSON config to your AI client), and direct REST endpoints for backend application integrations. Both channels use the same production APIs, the same data, and the same SLA. One APITier account covers both.
Which AI clients are supported?
Any MCP-compatible client: Claude Desktop, Cursor, Windsurf, and custom agent frameworks built on the MCP SDK. The APITier MCP server is client-agnostic — if the client supports MCP, it can use APITier tools.
What APIs are available for AI agents?
UK address validation and enrichment (Royal Mail PAF), email validation, phone validation, VAT number validation (HMRC/VIES), web content extraction, barcode generation (EAN-13, Code 128), and QR code generation. Each API is available as an MCP tool and a direct REST endpoint.
How does access control work for agents?
Tool access is subscription-gated. Only the APIs you subscribe to are exposed as MCP tools in your agent session. Unsubscribed APIs are invisible to the agent. When a subscription expires, those tools are removed from the next MCP session automatically.
Can I use the same API key for agent calls and application calls?
Your REST API key works for direct application calls. MCP tool calls use a separate MCP key. Both authenticate against the same APITier account and consume credits from the same subscription plan — they are just different authentication methods for different access patterns.
Is there a sandbox or test environment for agent development?
Every new account gets 20 free requests across the APIs you subscribe to. These work against the production endpoints — the same data, the same format, the same response structure — so there is no environment gap between development and production.
What SLA applies to MCP tool calls?
The same SLA as the underlying production API: 99.9% uptime and sub-2 second response times at the 95th percentile. MCP tool calls are not treated differently from direct REST calls in terms of performance guarantees.
Sign up free, subscribe to the APIs your agents need, and connect via MCP or direct REST in minutes.