Service Objects vs RevAddress: What Quote-Only Address Validation Pricing Costs in 2026

Service Objects has sold address validation longer than most of the field has existed. Its DOTS Address Validation - US service takes an unstandardized address, matches it against USPS data, and returns a standardized, deliverable result with a Delivery Point Validation code. It is CASS-certified, it runs over REST or SOAP, and it has a deep catalog of related validators for phone, email, geocoding and lead scoring. For a team that wants one vendor across many data-quality problems and is comfortable with an enterprise sales motion, it is a serious product.

Most developers evaluating it are not running that procurement. They need US addresses validated to USPS standards, they want to read a price off a page, and they want a POST endpoint working before lunch. That gap is what this post is about.

It does not contain an invented Service Objects price, because Service Objects does not publish one and a made-up per-transaction rate is worse than no rate at all. What it contains instead is what Service Objects does publish, what its free trial actually is, what a quote has to pin down before you can compare it to anything, and what published flat pricing looks like on the other side. RevAddress, which publishes this site, is that flat-rate comparison.

What Service Objects publishes about price

The dollar figure is quote-only. Service Objects’ G2 profile for DOTS Address Validation - US states the product has not provided pricing information and directs buyers to contact the vendor for current pricing. A Gartner listing for the broader DOTS platform describes a pricing model based on transaction volume, with tiered packages and both pay-as-you-go and subscription options, but no rates. SoftwareSuggest carries a starting-price field with no figure in it. That is standard for enterprise data-quality software and is not a criticism. It does mean any per-transaction number you see quoted for this product online is somebody’s negotiated contract, not a rate card, and you cannot budget against it.

What is published is the shape of the meter: you buy transactions, by volume, as a package or a subscription. A successful lookup consumes a transaction. The two questions that follow from that, and that the website cannot answer, are what a transaction costs at your volume and whether unused transactions expire. Both live in a quote.

What the free trial actually is

This is the number most comparisons get wrong. Service Objects’ DOTS Address Validation - US resource page offers 500 complimentary transactions for testing. That is a one-time allotment to prove the integration works, not a recurring monthly allowance. The same 500-transaction offer appears on several of its product pages, so read it as a general trial, not an ongoing free tier.

RevAddress’s free tier is a different instrument. It is 1,000 requests every month, no card, no expiry, for Census standardization, geocoding and address extraction. You can run production traffic on it inside that cap indefinitely. When you compare the two, compare a one-time 500-transaction test against a standing 1,000-a-month floor, not against each other as if both renewed.

What a quote has to pin down

Because the rate is negotiated, the useful work is knowing what to negotiate. Six questions decide whether a Service Objects quote is comparable to a published price:

1. The per-transaction rate, and the volume band it applies to. Ask for the full ladder, not the entry number. The effective rate at your real volume is the one that matters.
2. Whether transactions expire. A package of transactions with a clock on it prices very differently from one without. If unused transactions lapse at the end of a term, your effective rate is set by your lowest month, not your average.
3. The annual minimum. A commitment sized above your real volume raises your true per-lookup cost for every lookup you make. Enterprise quotes are usually annual.
4. Whether a failed or unmatched lookup consumes a transaction. Some vendors meter only successful matches. Get the rule in writing, not in a sales email.
5. Overage treatment. Hard stop, soft overage at the contract rate, or soft overage at a penalty rate. The third is common and expensive.
6. Term, renewal and price-lock. Multi-year commitments usually buy a lock. Auto-renewal usually carries an opt-out window measured in months.

Every one of those is knowable before you sign, and none is knowable from a website. Budget the procurement time, not just the money.

The number to compare a quote against

Flat monthly pricing gives you the other half of that comparison. These are published, they are the same figures the API meters against, and they do not move with your usage inside the plan’s request cap:

RevAddress pricing, which renders from the catalog the API bills against.

One caveat before you use that table. What those prices buy depends on whose USPS license the postal data runs on, and the next section is that answer. Reading the table without it would make it look like something it is not.

Which license the USPS data runs on

Service Objects holds its own USPS relationship and refreshes its CASS-certified address data on the Postal Service’s cycle. You pay Service Objects, and you never touch a USPS agreement.

RevAddress is built the other way round. Two routes:

Census-based standardization, at no cost. Standardization, geocoding and address extract run against the US Census Bureau’s public address inventory. 1,000 requests a month on the free key, no USPS license, no per-lookup fee. It puts an address into correct postal form and returns street-level coordinates. It does not return DPV, ZIP+4 or a USPS deliverability flag, and the response says so in classification and userMessage rather than leaving you to infer it. RevAddress is not a CASS-certified vendor and does not perform NCOALink processing.

The full USPS suite on your own license. You sign the USPS Addresses API agreement, you pay the USPS fee curve directly, and you point RevAddress at your credentials. The whole postal stack then runs on your license and on this infrastructure: DPV verification with ZIP+4, CMRA, vacant and business flags, plus rates, service standards and tracking, with label creation and voids at the Pro tier. RevAddress manages the OAuth lifecycle, the rate-limit budget, the caching policy and the retries; the Postal Service relationship and its reporting stay in your name. USPS bills monthly consumption at a single tier and rounds partial thousands up, which at 25,000 lookups a month is $106.25 on top of the plan fee and at 100,000 is $400.

So a like-for-like total at 25,000 US lookups a month is $79 plus $106.25, or $185.25. At 100,000 it is $599. Those are the numbers to hold a quote against, and unlike a per-transaction rate they do not need renegotiating when your volume moves inside the tier. The USPS pricing breakdown walks the whole fee curve and the license process.

The CASS question, answered honestly

CASS certification is the part of this comparison a developer most often conflates with deliverability, and the two are not the same job.

CASS is the USPS program that certifies address-matching software: it checks that a product standardizes and codes addresses the way the Postal Service requires. Its headline purpose is qualifying mail for automation discounts, where a presort house or a high-volume mailer needs CASS-processed addresses and a documented CASS summary to claim those rates. Service Objects holds that certification, which is exactly right for that workflow.

Delivery Point Validation answers a narrower, operational question: can mail actually be delivered to this specific point. Y is a confirmed delivery point, N is not confirmed, D is confirmed but missing a secondary unit, S is a secondary that does not exist. That is the signal a checkout, a CRM import or a shipping label needs, and on a connected USPS license RevAddress returns it straight from the Postal Service’s own API.

So the honest split is this. If your requirement is CASS certification itself, for presort discounts or for a CASS summary your mail service bureau asks for, Service Objects or the USPS’s own licensed tooling is the right tool and this post is not arguing otherwise. If your requirement is deliverability verification at transaction time, at a price you can read today, that is the comparison this post is about.

The API surface, side by side

Service Objects’ recommended operation is GetBestMatches, called over REST or SOAP with your license key as a parameter. It returns a standardized address plus a DPV code, a DPVDesc, DPVNotes and a Corrections code. Over REST a GET looks roughly like this:

curl "https://sws.serviceobjects.com/AV3/api.svc/GetBestMatchesJson?\
Address=1600+Pennsylvania+Ave+NW&City=Washington&State=DC&PostalCode=20500&\
LicenseKey=YOUR_LICENSE_KEY"

RevAddress takes a flat JSON payload to POST /api/address/validate with the key in an X-API-Key header. A GET with query parameters works too.

curl -X POST "https://api.revaddress.com/api/address/validate" \
-H "X-API-Key: rv_live_your_key" \
-H "Content-Type: application/json" \
-d '{
  "streetAddress": "1600 Pennsylvania Ave NW",
  "city": "Washington",
  "state": "DC",
  "ZIPCode": "20500"
}'

With a USPS license connected, the response carries the standardized address, ZIP+4 and the DPV code, with the classification stated rather than left for you to infer:

{
"address": {
  "streetAddress": "1600 PENNSYLVANIA AVE NW",
  "city": "WASHINGTON",
  "state": "DC",
  "ZIPCode": "20500",
  "ZIPPlus4": "0003"
},
"additionalInfo": { "DPVConfirmation": "Y", "business": "Y", "vacant": "N" },
"resolution": {
  "classification": "deliverable_exact",
  "nextAction": "done",
  "userMessage": "USPS confirmed this address."
}
}

On the free key the shape is the same and the honesty is in the fields. There is no ZIP+4, no additionalInfo, and the classification says what actually happened:

{
"address": {
  "streetAddress": "1600 PENNSYLVANIA AVE NW",
  "city": "WASHINGTON",
  "state": "DC",
  "ZIPCode": "20500",
  "ZIPPlus4": null
},
"additionalInfo": null,
"verificationSource": "census_geocoder",
"coordinates": { "lat": 38.8977, "lng": -77.0365 },
"resolution": {
  "classification": "standardized_unverified",
  "nextAction": "upgrade_for_dpv",
  "userMessage": "Standardized against the U.S. Census Bureau master address file. USPS delivery-point (DPV) confirmation is not included on the free standardization tier."
}
}

A validator that returns the same shape whether or not it verified anything is the failure mode this design exists to avoid. Read classification, not a boolean.

Migrating US validation off Service Objects

You do not have to move everything. Keeping Service Objects for phone, email or international validation while routing US address volume elsewhere is a common shape.

1. Get a free key at revaddress.com/signup. 1,000 requests a month, no card, no call.
2. Swap the call. The REST or SOAP GetBestMatches becomes POST /api/address/validate. The LicenseKey parameter becomes an X-API-Key header, which keeps the key out of your URLs and your logs.
3. Flatten the payload. Top-level streetAddress, city, state, ZIPCode. Aliases resolve, so street_address, address1, line1, zip and zip_code will not return a 400.
4. Map the result. Service Objects’ DPV code, DPVNotes and Corrections values map to resolution.classification plus, on a connected USPS license, additionalInfo.DPVConfirmation. The four DPV letters mean the same thing on both sides.
5. Move bulk jobs to POST /api/batch/validate, 50 per call, each settled independently so one malformed record returns its own error rather than failing the batch.
6. Run both in parallel on real traffic before the renewal date, not after. A free key makes that cost nothing.

Typical time for a single US validate call: a few hours.

Which one to pick

Service Objects, if you need CASS certification for presorted-mail discounts, want one vendor across address, phone, email and geocoding, are comfortable with a sales cycle and an annual commitment, or need the enterprise procurement posture that comes with it.

A published flat price, if your volume is US-centric, you want a number you can read today and forecast next quarter, you want the raw USPS DPV code on your own license rather than a transaction package with a clock on it, or you want to ship before a procurement cycle finishes. If a one-time list cleanse is the whole job and an API is not, List Clean takes a CSV from $19 with no contract and no per-record metering.

Sources

• Pricing-not-provided status and the contact-vendor direction: the Service Objects DOTS Address Validation - US listing on G2. The transaction-volume model with pay-as-you-go and subscription options: the DOTS platform listing on Gartner. The empty starting-price field: the Service Objects listing on SoftwareSuggest. Read October 2026.
• The 500 complimentary transactions, the GetBestMatches operation, the REST and SOAP surface, and the DPV, DPVNotes and Corrections response fields: the Service Objects DOTS Address Validation - US product page and its developer documentation. Read October 2026. Re-confirm the 500-transaction wording against the live product page immediately before this post is published.
• CASS certification and the USPS address-data refresh cycle: Service Objects’ USPS address validation explainer. Read October 2026.
• USPS fee tiers: the USPS Addresses API Tech Sheet on PostalPro.
• RevAddress plan prices and request caps come from the pricing page, which renders from the same catalog the API meters against.

Service Objects’ rate is negotiated, so nothing here can be a price comparison in the strict sense. Take the flat figures to the quote conversation and make them do that work.

Start here

• Get a free API key — 1,000 requests a month, no card
• Full pricing · API reference
• USPS API pricing in 2026 — the fee curve and the license process, in full
• Clean one file instead — from $19