Address Parsing for AI Agents

Overview

Street Address Parser works by analyzing the US street address provided and splitting it into its components: street number, directional prefix and suffix, street name, street type, secondary unit, city, state and ZIP code. Intersections such as "Main St and 5th Ave" come back as two streets. PO boxes, written as PO Box, P.O. Box, POB or Post Office Box, come back as sec_unit_type "PO Box" with the box number, city, state and ZIP code. With standardize=true the response adds a standardized block: the address type is free, while the delivery line, last line and ZIP+4 extension require a paid plan. The parser formats what you send; it does not check the address against postal records.

Live Test Address Parsing for AI Agents Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as AddressParsingforAIAgents. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "AddressParsingforAIAgents",
  "arguments": {
    "address": "1600 Amphitheatre Parkway, Mountain View, CA 90210"
  }
}

You do not name the tool yourself; the model picks it. Asking about 1600 Amphitheatre Parkway, Mountain View, CA 90210 in the terms this source covers is enough for it to reach for AddressParsingforAIAgents on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

{
  "status": "ok",
  "error": null,
  "data": {
    "address": "1600 Amphitheatre Parkway, Mountain View, CA 90210",
    "parsed": {
      "streetNumber": "1600",
      "streetType": "Pkwy",
      "streetAddress": "Amphitheatre",
      "cityName": "Mountain View",
      "stateName": "CA",
      "zipCode": "90210"
    },
    "standardized": {
      "addressType": "street",
      "deliveryLine1": "1600 Amphitheatre Pkwy",
      "lastLine": "Mountain View, CA 90210",
      "zipPlus4": null
    }
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at parsed.streetNumber: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Mailing Label Printing

To prepare bulk shipping labels, fulfillment software isolates street numbers, street types, and ZIP codes from freeform buyer text.

Real Estate Ingestion

When property portals ingest raw MLS remarks, backend pipelines extract city and state abbreviations to index homes into regional search databases.

Voter Registration Intake

Separate unformatted residential entries into discrete building numbers and street names to match voter registrations against county records.

Tax Jurisdiction Lookup

Accounting platforms assign municipal sales tax rates by breaking customer billing strings into standardized city names and state codes.

Other ways to use Address Parsing for AI Agents

Set up Address Parsing for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Parsers: