Address Parser Skill

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 Parser Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as AddressParserSkill. 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.

Tool call

{
  "name": "AddressParserSkill",
  "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 skill covers is enough for it to reach for AddressParserSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill 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": {
    "vervekit": {
      "url": "https://api.vervekit.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.

Argument	Type	Description
`address`Required	string	The street address to parse
`standardize`Optional	boolean	Add a standardized block: the address type, plus on paid plans the delivery line, last line and ZIP+4

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.

Result

{
  "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.

Field	Type	Example	Description
`address`	string	`1600 Amphitheatre Parkway, Mountain View, CA 90210`	The original street address provided for parsing
`parsed`	object	`{…}`
`parsed.streetNumber`	string	`1600`	House or building number from the address
`parsed.streetType`	string	`Pkwy`	Abbreviated street type like Pkwy, St, Ave; absent for a PO box
`parsed.streetAddress`	string	`Amphitheatre`	The name of the street parsed from address; absent for a PO box
`parsed.cityName`	string	`Mountain View`	City name extracted from the address
`parsed.stateName`	string	`CA`	State abbreviation parsed from address
`parsed.zipCode`	string	`90210`	Postal code extracted from the address
`standardized`	object	`{…}`	Standardized form of the address, returned when standardize=true
`standardized.addressType`	string	`street`	street, poBox or intersection
`standardized.deliveryLine1`Premium	string	`1600 Amphitheatre Pkwy`	Street line in mailing-label order, e.g. 123 N Main St Apt 4B, PO Box 55, or Main St & 5th Ave
`standardized.lastLine`Premium	string	`Mountain View, CA 90210`	City, state and ZIP (with ZIP+4 when given) as one line, e.g. Springfield, IL 62701-1234; null when the city or state could not be read
`standardized.zipPlus4`Premium	object	`null`	The four-digit ZIP+4 extension when the input carries one, else null

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.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

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 Parser Skill

Set up Address Parser Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →