How do I find my Zip-codes.com API Key?

Log in to your [**Zip-codes.com account**](https://www.zip-codes.com/account/login.asp), and you will find your API Key under the 'API Settings' or 'My Account' section. Copy and paste it below.

Does it support Canadian postal codes?

Yes. Zip-codes.com provides extensive data for both United States ZIP codes and Canadian Postal Codes (forward sortation areas).

Can the agent calculate distances?

Yes. The `get_zip_distance` tool calculates the point-to-point distance in miles between any two valid ZIP codes instantly.

ZIP Codes API MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: ZIP Codes API
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to ZIP Codes API through Vinkius, pass the Edge URL in the `mcps` parameter and every ZIP Codes API tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="ZIP Codes API Specialist",
    goal="Help users interact with ZIP Codes API effectively",
    backstory=(
        "You are an expert at leveraging ZIP Codes API tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in ZIP Codes API "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About ZIP Codes API MCP Server

Empower your AI agent to orchestrate your entire geographic research and ZIP code auditing workflow with ZIP Codes API, the authoritative source for United States and Canadian location data. By connecting the Zip-codes.com API to your agent, you transform complex logistics searches into a natural conversation. Your agent can instantly retrieve detailed ZIP metadata, audit distances between locations, and identify all ZIP codes within a specific radius without you ever touching a manual lookup tool. Whether you are conducting market analysis or managing regional logistics, your agent acts as a real-time geographic consultant, ensuring your data is always verified and precise.

When paired with CrewAI, ZIP Codes API becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ZIP Codes API tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

ZIP Auditing — Retrieve high-resolution geographic details for any 5-digit ZIP code, including city, state, and county information.
Radius Oversight — Find all ZIP codes within a specific mile radius of a starting point to identify regional clusters instantly.
Distance Intelligence — Calculate the exact distance between any two ZIP codes to assist in logistics and delivery planning.
Regional Discovery — Find all ZIP codes associated with a specific city, state, or county to maintain a clear view of geographic distribution.
Metadata Discovery — Retrieve latitude and longitude coordinates for specific ZIP codes to maintain visual and spatial context.

The ZIP Codes API MCP Server exposes 6 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect ZIP Codes API to CrewAI via MCP

Follow these steps to integrate the ZIP Codes API MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 6 tools from ZIP Codes API

Why Use CrewAI with the ZIP Codes API MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with ZIP Codes API through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

ZIP Codes API + CrewAI Use Cases

Practical scenarios where CrewAI combined with the ZIP Codes API MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries ZIP Codes API for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries ZIP Codes API, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain ZIP Codes API tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries ZIP Codes API against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

ZIP Codes API MCP Tools for CrewAI (6)

These 6 tools become available when you connect ZIP Codes API to CrewAI via MCP:

find_zips_by_city

Find all ZIP codes associated with a city and state

find_zips_by_county

Find all ZIP codes in a specific county

find_zips_by_state

Find all ZIP codes in a specific state

find_zips_in_radius

Find all ZIP codes within a specific mile radius of a starting ZIP

get_zip_details

Get geographic and demographic details for a specific ZIP code

get_zip_distance

Calculate the distance between two ZIP codes

Example Prompts for ZIP Codes API in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with ZIP Codes API immediately.

"Get details for ZIP code '90210' using ZIP Codes API."

"Find all ZIP codes within a 10 mile radius of '10001' (New York)."

"Calculate the distance between '10001' and '90210'."

Troubleshooting ZIP Codes API MCP Server with CrewAI

Common issues when connecting ZIP Codes API to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

ZIP Codes API + CrewAI FAQ

Common questions about integrating ZIP Codes API MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.