Index › Products › Google Maps Address Validation API · October 2026 Edition

1 category · Named, not ranked

Google Maps Address Validation API

7Judge labels

1First choices

3Negative labels

5 / 14Models named it

1Category

October 2026 Edition. Every number here is derived from the raw labels under vendor table v2026-10-05.2, every buyer segment counted.

Standing

5 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. Google Maps Address Validation API was named 5 times in Address verification, where Smarty led with 47%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small business34 of 81

under the label threshold

Mid-market20 of 108

under the label threshold

Enterprise31 of 84

under the label threshold

In address verification · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Google Maps Address Validation API for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant	Since September 2026
Address verification tools	GTM data and infrastructure	2%	20 of 108	60%	5	under 10 labels · led by Smarty at 47%

Movement

This is the first edition on this tier, so no move can be computed for Google Maps Address Validation API yet. From the next edition this section shows, per buyer segment and per category, whether its share moved by more than the measured noise floor.

By model

How each model treated Google Maps Address Validation API across every prompt where it was named for a mid-market B2B company. Fourteen models, six prompts per category.

ShowHide

Model	First choice	Alternative	Negative	Labels
Claude Haiku 4.5	0	0	1	1
GPT-5.4 mini	0	0	0	0
Gemini 3.5 Flash	0	1	1	2
Perplexity Sonar	0	0	0	0
Grok 4.1 Fast	0	0	0	0
Mistral Small	1	0	0	1
DeepSeek V4 Flash	0	0	1	1
Llama 4 Maverick	0	0	0	0
Qwen 3.7 Flash	0	0	0	0
Kimi K2	0	0	0	0
GLM 4.7 FlashX	0	0	0	0
MiniMax M2.5	0	0	0	0
GPT-6 Luna	0	0	0	0
Muse Glimmer 30B	0	0	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct1 labelNone

Paraphrase3 labels1

Comparative0 labelsNone

Budget-constrained2 labelsNone

Scale-constrained0 labelsNone

Negative1 labelNone

First choiceAlternativeMentionNegative7 labels in all, every segment counted; 1 of the 1 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“For most mid-sized B2B companies, Google Maps Address Validation API is the best overall choice” Mistral Small · Address verification · paraphrase prompt · first choice

“Google Maps is incredibly accurate and highly cost-effective for small-to-medium-sized transaction volumes.” Gemini 3.5 Flash · Address verification · budget prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“here are address verification tools you should avoid or be cautious about: ## Google Maps Address Validation API” Claude Haiku 4.5 · Address verification · negative prompt · hard negative

“Avoid for B2B: Google Maps Address Validation API” Gemini 3.5 Flash · Address verification · paraphrase prompt · hard negative

“Pay-as-you-go, but can get expensive at higher volumes and lacks USPS standardization” DeepSeek V4 Flash · Address verification · budget prompt · soft negative

Named alongside

The products named in the same answers as Google Maps Address Validation API, over the 7 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Google Maps Address Validation API was named but was not.

ShowHide

ProductSame answerTook the first choice insteadHead to head

Smarty4 of 74Not among the top eight

Melissa4 of 70Not among the top eight

PostGrid Address Verification3 of 71Not among the top eight

Geocodio1 of 71Not among the top eight

USPS Address API1 of 71Not among the top eight

Data81 of 70Not among the top eight

EasyPost1 of 70Not among the top eight

Geoapify1 of 70Not among the top eight

Loqate1 of 70Not among the top eight

Melissa Address Validation API1 of 70Not among the top eight

A head-to-head page exists where both products are among a category's top eight. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Google Maps Address Validation API. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 7 of the 7 answers that named Google Maps Address Validation API and are not a share of its labels.

Domains cited

smarty.com5

guideflow.com4

postgrid.com4

developers.google.com3

melissa.com3

apollotechnical.com2

g2.com2

infomsp.com2

lob.com2

opencart.com2

No domain is on file for Google Maps Address Validation API, so its own site is not marked.

Pages cited

guideflow.com/blog/address-verification-software4

melissa.com/address-experts/google-address-validation-vs-melissa-address-validation-global3

smarty.com/compare/smarty-address-verification-alternatives3

smarty.com/products/us-address-verification3

apollotechnical.com/address-verification-apis-for-saas-and-b2b-marketing-teams2

developers.google.com/maps/documentation/address-validation/requests-validate-address2

infomsp.com/top-10-address-verification-software2

melissa.com/address-experts/google-address-validation-vs-melissa-address-validation-us-api2

Pages are listed as the models cited them.

Follow Google Maps Address Validation API

An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.

Already following? Everything you follow, with a stop for each.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Google Maps Address Validation API's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Google Maps Address Validation API, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

What a new claim receivesHide what a new claim receives

A new claim receives the current edition's vendor brief for Google Maps Address Validation API by email, built from the raw record of the edition. It shows:

where Google Maps Address Validation API is named, by buyer and by framing, and which cells hold its first choices;
the claims the models make when they name it, ranked, with the strongest and the weakest quoted;
its vocabulary against the segment leader's, and the pages the models cited;
who was chosen in the answers that did not name Google Maps Address Validation API, and every reason the record gives;
a battlecard for each top rival: the head-to-head split, why they win, and the reservation quoted against them;
one page of published figures cleared to show a buyer.