Lob vs RevAddress: Address Verification Pricing and the Plan Underneath It

Lob is a direct-mail platform. Postcards, letters, checks, certified mail, an in-transit tracking dashboard, and a print delivery network. Address verification is a line item on those plans, priced per verification, and it exists to keep the mail deliverable.

RevAddress is a USPS address layer. Standardization and geocoding against Census Bureau data with no license needed, then DPV, ZIP+4, rates, and service standards through the USPS v3 REST API on your own USPS credentials. Nothing gets printed.

Teams end up comparing the two for one reason: they adopted Lob to verify addresses in a checkout or a CRM and never touched the mail side.

What Lob charges, as published

Lob’s plan tiers are mail tiers. The verification rate is attached to whichever one you are on, so the cheapest per-verification number is not reachable from the cheapest plan.

Read the second column and the fourth together. The $0.009 verification is real, and reaching it means a $550 monthly plan plus a $450 verification bundle. The $25 bundle for 1,000 verifications sits on the Startup plan at $260 a month. Only the Developer plan has no monthly floor, and its rate is $0.05, the highest of the three.

International verification follows the same shape: $0.07 on Developer, $0.06 on Startup with 500 included for $30, $0.055 on Growth with 10,000 included for $550.

Cost at volume

Two different Lob routes are worth pricing: Developer, where you pay $0.05 per verification and nothing else, and the bundle route, where the cheaper unit rate carries a plan underneath it.

The Lob columns are arithmetic on Lob’s published rates: Developer is volume times $0.05; the bundle route is the verification bundle plus overage plus the plan price it requires. The RevAddress column is the plan price from the pricing page plus the USPS Addresses API fee for that month’s lookups, which USPS bills to your Enterprise Payment Account, not to us.

Three things that table does not say out loud.

The units are not the same. Lob meters verifications. RevAddress meters API requests, and every call counts against the same monthly budget, whether it is a validation, a rate quote, or a batch job. If your workload is one validation per order and nothing else, the columns line up. If it is four calls per order, divide the RevAddress limit by four.

DPV requires your own USPS license. The USPS column is not optional for deliverability work, and it is not the whole cost: the license is a signed agreement with a funded Enterprise Payment Account behind it, and signatures take weeks. The CRID and MID enrollment guide walks the sequence. Standardization and geocoding need none of it.

Lob’s plan buys mail capacity you may not want. If you are also mailing 75,000 pieces a year, the $260 is not overhead, it is the product. If you are not, it is the price of a verification rate.

What comes back from each

import lob

lob.api_key = "live_xxx"

verification = lob.USVerification.create(
  primary_line="1600 Pennsylvania Ave NW",
  city="Washington",
  state="DC",
  zip_code="20500",
)

# deliverability: deliverable | deliverable_missing_unit |
#   deliverable_incorrect_unit | deliverable_unnecessary_unit | undeliverable
if verification.deliverability == "deliverable":
  print("Valid")
else:
  print(f"Issue: {verification.deliverability}")

from usps_v3 import USPSClient

client = USPSClient(api_key="rv_live_your_key_here")

result = client.addresses.validate(
  street_address="1600 Pennsylvania Ave NW",
  city="Washington",
  state="DC",
  zip_code="20500",
)

if result.dpv_confirmation == "Y":
  print("Valid, DPV confirmed")
else:
  print(f"Not confirmed: DPV={result.dpv_confirmation}")

Both calls reach USPS data. They differ in what survives the trip back.

Lob returns a deliverability value from a fixed set, and its set is more expressive than most: deliverable_missing_unit and deliverable_incorrect_unit are genuinely useful distinctions that a plain boolean loses. RevAddress returns the raw DPV confirmation code plus the DPV footnotes underneath it, which is the same information at a lower level, with the footnote strings that say why.

The practical difference shows up in triage. A batch fails overnight. Sorting by DPV code separates the addresses missing an apartment number, the addresses carrying an apartment number the building does not have, and the addresses USPS has never seen, because each is a different fix and a different email to a different team. Lob’s enum gets you most of the way there for the first two. The footnotes are what tell you about a vacant flag, a CMRA, or a no-stat address, and those are USPS fields that a normalized deliverability value has no room for.

Where each one stops

Honest limits on both sides, because the wrong pick here is expensive.

Lob does not ship packages. No rates, no labels, no tracking numbers. Verification is the last step Lob takes toward a parcel; after that you are on a second API.

Lob has no BYOK. You use Lob’s data access, on Lob’s terms, at Lob’s rate. That is a feature if you never want to sign a USPS agreement, and a constraint if you need your own USPS reporting or your own direct line to the Postal Service.

RevAddress is US only. No international verification at any tier. If a meaningful share of your addresses are outside the US, this comparison ends here and Lob wins it.

RevAddress does not print or mail anything. Not a gap we intend to close.

Label creation on RevAddress runs on your own USPS license, on the Pro plan. We do not create labels on our credentials for you, because postage has to be paid by the entity that owes it. Tracking and pickup endpoints are limited-rollout surfaces; request access before building an operation on them.

When Lob is the right choice

• You send physical mail. Postcards, letters, checks, certified mail at scale. This is Lob’s core competence and the reason the plans are priced the way they are.
• You verify addresses outside the US. Lob covers international; RevAddress does not.
• You are already on a Startup or Growth plan for mail. The verification bundle is then a marginal add-on, the plan cost is already sunk, and $0.009 per address is a very good rate.
• You want zero USPS paperwork. Lob absorbs the postal relationship entirely. No license, no Enterprise Payment Account, no countersignature to wait on.
• In-transit mail tracking and a print delivery network are the job. Nothing in this comparison substitutes for those.

When RevAddress is the right choice

• You adopted Lob for verification and never mail anything. The Developer plan at $0.05 works out to $250 a month at 5,000 verifications, against $29 plus a USPS fee of $22.50 for the same volume. At 10,000 the gap is $500 against $124.
• You need the raw USPS fields. DPV code, DPV footnotes, ZIP+4, carrier route, CMRA, vacancy, and business flags come back as USPS returns them, on your own USPS license.
• You want the postal relationship in your own name. BYOK means your CRID, your MID, your Enterprise Payment Account, your USPS reporting, and your rate limits. Every plan supports it, including Free.
• You need standardization and geocoding without a license at all. The free tier runs 1,000 requests a month against Census Bureau data with no USPS credentials and no card. It will not tell you whether mail arrives. It will get an address into correct postal form with coordinates attached, which for list hygiene is the whole job.
• Your next step after validating is a USPS operation. Rates and service standards on Starter, batch validation at 50 addresses per call on Growth, label creation and voids on Pro. All on your own license.

Migrating a validation integration

For a standalone Lob verification call, this is a couple of hours of work.

1. Get a free key at revaddress.com/signup. No card, 1,000 requests a month.
2. Install the SDK: pip install usps-v3 or npm install usps-v3.
3. Map the response. Lob’s deliverable maps to DPV Y. deliverable_missing_unit maps to D. deliverable_unnecessary_unit maps to S. undeliverable maps to N. deliverable_incorrect_unit has no single DPV equivalent and shows up in the footnotes, so read those rather than forcing a code.
4. Replace the call, using the code above.
5. Run both in parallel on real addresses before you cut over. Free-tier volume is enough to sample.
6. Connect your USPS app from the dashboard when you need DPV rather than standardization. Roughly three minutes once the license exists; weeks if it does not yet.
7. Keep Lob for mail and for international. The two coexist without conflict.

Sources

• Lob, Pricing and the address-verification plan comparison, checked August 23, 2026. Plan prices, mailing caps, and per-verification rates are Lob’s published figures; the volume math above is arithmetic on them.
• USPS, Addresses API Tech Sheet, fee schedule effective August 1, 2026, as published August 13, 2026. The single-tier curve and the rounding rule are USPS’s.
• RevAddress plan prices and limits come from the pricing page, which renders from the same catalog the API meters against.

Lob restructures its plans periodically; the Business tier that appeared in the June 2026 version of this comparison is no longer published. Check both pricing pages before you budget.

Start today

• Get a free API key — 1,000 requests a month, no card
• Full pricing and the API reference with a live try-it
• Not building an integration? Clean a list once, from $19