{"uid":"cap_A8WMBwq2yfbeye5wZPo8E","slug":"fittings-address-standardizer-913d0ed3","name":"fittings Address Standardizer","description":"Normalize a free-text US street address into its USPS-style standardized one-line form plus parsed components: house number range, directionals, street name, suffix, city, state and 5-digit ZIP.","url":"https://fittings.sh/v1/addr/standardize","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET"],"type":"string"},"queryParams":{"type":"object","required":["address"],"properties":{"address":{"type":"string","description":"Free-form US street address, at most 200 characters"}}}},"additionalProperties":false}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.003","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.003/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_DkvH4Q5RTy3zoVevKLi1r","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.003","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Normalizes a free-text US street address into USPS-style standardized format with parsed components including house number, directionals, street name, suffix, city, state, and ZIP.","exampleAgentPrompt":"Can you standardize this address into proper USPS format and pull out the individual components — I have '123 main st apt 4, new york ny 10001'?","exampleUseCases":[{"title":"E-commerce checkout address cleanup","prompt":"The customer typed '456 w elm street, chicago il 60601' in the checkout form — can you standardize that into the official USPS postal format and give me the parsed components like street number, direction, and ZIP?"},{"title":"CRM data normalization","prompt":"I've got a messy address entry in our CRM that says '22 south broadway ste 100 denver co 80209' — please normalize it to the proper USPS one-line form and break out the street name, suffix, city, state, and ZIP separately."},{"title":"Mail merge address formatting","prompt":"Before I run this mail merge, can you clean up this address — '99 park ave n, new york, new york, 10016' — and give me the standardized USPS version plus each parsed field?"}],"resultDescription":"Returns the USPS-style standardized one-line address string alongside individually parsed components: house number or range, pre-directional and post-directional, street name, street type suffix, city name, two-letter state abbreviation, and 5-digit ZIP code.","failureModes":["Address cannot be parsed or recognized — returns an error or empty result","Non-US address submitted — coverage is US-only, international addresses will fail","Address string exceeds 200 characters — rejected by input validation","Ambiguous or incomplete address (e.g. missing city/state/ZIP with no context) — may return low-confidence or no result","Malformed or gibberish input — returns parse error"],"whenToPreferThis":"Choose this endpoint when you need to normalize and parse a raw, user-entered US address string into structured USPS-compliant components — particularly useful for data cleaning, form validation, and pre-processing before geocoding. Prefer it over geocoding endpoints when lat/lng coordinates are not needed and the goal is purely address standardization and component extraction. It is faster and cheaper than full geocoding for address formatting tasks alone.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T12:49:56.960Z","isFirstParty":false}