Geocodio vs RevAddress — The 2026 Price Increase and the CASS Gap

For teams using Geocodio to clean or verify US addresses, two facts deserve a second look in 2026.

First, on February 1, 2026, Geocodio doubled its pay-as-you-go price, from $0.50 to $1.00 per 1,000 lookups, and raised its Self-Service Unlimited plan from $1,000 to $1,350/month for new customers.

Second, and older than the price change, Geocodio is not CASS certified, as Geocodio itself states. That does not matter for plotting points on a map. It matters for validating addresses for shipping or mail, where USPS deliverability (DPV) is the question.

This post is about that distinction: geocoding versus address validation. The two look similar and are priced similarly, and teams reach for the wrong one. What follows covers where Geocodio is the better tool, where it is not, and what a USPS-native, flat-rate alternative looks like.

The February 2026 price change

Geocodio’s pricing update took effect February 1, 2026. The headline numbers:

Geocodio still includes 2,500 free lookups per day (~75,000/month), so low-volume geocoding stays free. For a few thousand pure coordinate lookups a day, Geocodio is hard to undercut on price.

The problem shows up at two edges. Above the free daily cap, pay-as-you-go now costs twice the old rate. A mid-cycle doubling also shows that usage-metered pricing is exposed to changes the customer does not control.

Geocoding vs USPS deliverability

This is the part that matters more than the price.

Geocodio is a geocoder. You send it an address, it returns latitude/longitude, a match accuracy score, and optional data appends (Census blocks, congressional districts, timezone, ACS demographics). It does that well.

It is not a CASS/DPV address validator. Geocodio does not carry USPS CASS certification, and its match is its own rather than a USPS Delivery Point Validation. That means it does not give a USPS answer to the questions a shipping or mailing workflow asks:

• Is this a real, deliverable delivery point (DPV confirmed), or a plausible-looking street that geocodes fine?
• Is the unit/apartment number valid, or missing (DPV secondary flags)?
• Is it a CMRA (commercial mail receiving agency), a vacant address, or no-stat?
• What’s the ZIP+4 and standardized USPS form the Postal Service will route on?

A coordinate on a map answers none of those. An address can geocode perfectly and still be undeliverable. If you’re printing labels, mailing checks, or gating checkout, geocoding accuracy is the wrong test; the test is USPS DPV.

RevAddress, which publishes this site, validates against USPS’s own DPV data when a USPS license is connected to the account, and returns the standardized, deliverable form rather than a coordinate.

Metered vs flat pricing

Geocodio meters per lookup (with the free daily allowance). RevAddress is flat monthly, and cached repeat lookups do not count against the plan.

For high-volume pure geocoding, Geocodio’s metered model can cost less than a flat plan. For address validation, where the same mailing lists are re-checked, a checkout is gated and the bill has to be forecast, flat pricing with free cached repeats is the better fit, and the number does not move mid-year.

Side-by-side code

Geocodio returns coordinates; RevAddress returns a deliverability answer.

curl "https://api.geocod.io/v1.7/geocode\
?q=1600+Pennsylvania+Ave+NW+Washington+DC\
&api_key=YOUR_KEY"

# Returns lat/lng + an accuracy score:
# {
#   "results": [{
#     "formatted_address": "1600 Pennsylvania Ave NW, Washington, DC 20500",
#     "location": { "lat": 38.897675, "lng": -77.036547 },
#     "accuracy": 1,
#     "accuracy_type": "rooftop"
#   }]
# }
# No DPV. No CMRA/vacant/no-stat. No deliverability verdict.

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"
}'

# Returns the USPS-standardized, deliverable form:
# {
#   "streetAddress": "1600 PENNSYLVANIA AVE NW",
#   "city": "WASHINGTON", "state": "DC",
#   "ZIPCode": "20500", "ZIPPlus4": "0003",
#   "dpvConfirmation": "Y",
#   "dpvCMRA": "N", "vacant": "N"
# }

RevAddress also accepts field-name aliases (street_address, address1, line1, zip and zip_code all work) and batch validation with fault isolation: one bad address never fails the whole batch.

curl -X POST "https://api.revaddress.com/api/batch/validate" \
-H "X-API-Key: rv_live_your_key" \
-H "Content-Type: application/json" \
-d '{"addresses": [
  {"streetAddress": "1600 Pennsylvania Ave NW", "city": "Washington", "state": "DC"},
  {"streetAddress": "350 Fifth Avenue", "city": "New York", "state": "NY"}
]}'

Feature comparison

When Geocodio is the right tool

For a real set of jobs, Geocodio is the better choice, and a comparison post is no reason to switch.

• You need coordinates, not deliverability: mapping, spatial analysis, distance and routing, plotting customers.
• Data enrichment is the point: Census blocks, congressional districts, ACS demographics and timezone appends on every row of a large file.
• Bulk one-off geocoding of a large file where the 2,500/day free tier covers you.
• Permissive data-usage rights matter to your product; Geocodio is unusually liberal here.

If any of those is your job, Geocodio is well-built and worth keeping.

When RevAddress is the right tool

• You’re validating addresses for shipping, mail, or checkout and need USPS DPV deliverability, not a coordinate.
• You need the USPS-standardized form + ZIP+4 the Postal Service will route on.
• You want CMRA / vacant / no-stat flags to catch undeliverable or fraud-adjacent addresses.
• You re-validate the same lists repeatedly and want cached repeats to be free.
• You want a flat, forecastable bill that doesn’t double mid-year.

Migration checklist

Moving an address-validation workload off Geocodio takes about an afternoon.

1. Get a RevAddress key: free, 1,000 requests/mo, no card. Create a key.
2. Swap the request shape: Geocodio is a GET /geocode?q=…; RevAddress is a POST /api/address/validate with structured fields (streetAddress, city, state). Field aliases mean your existing address1/zip keys work as-is.
3. Read deliverability, not coordinates: replace your accuracy/location checks with dpvConfirmation, dpvCMRA, and vacant, which test deliverability rather than map-match quality.
4. Move bulk jobs to batch: replace CSV uploads with POST /api/batch/validate. One bad row won’t fail the batch, and repeat addresses hit the 24-hour cache for free.
5. Keep Geocodio for what it does well: if you still need lat/lng or demographic appends, run it in parallel, with each API on the job it fits.

Full endpoint and field reference: API docs.

RevAddress validation, pricing and caching

• USPS-native validation: DPV deliverability against USPS’s own data on a connected USPS license, not a third-party map match.
• Flat pricing: $29 Starter / $79 Growth / $199 Pro, free 1,000 requests/mo. No per-lookup metering, no mid-year doubling.
• Batch with fault isolation: Promise.allSettled semantics; one failure never kills the batch.
• 24-hour cache: cleaning the same list twice costs nothing the second time.

Geocodio for coordinates, RevAddress for DPV

Geocodio is a strong geocoder that got more expensive in February 2026 and was never a CASS/DPV address validator. If you need coordinates and data enrichment, it is a fine tool to keep. A team using it to validate addresses for shipping or mail is paying, now double, for a map match where it needed USPS deliverability. RevAddress returns the DPV answer, on a connected USPS license, at a flat price.

For more on how metered address APIs compare, see Smarty vs RevAddress, Google Address Validation pricing, and Melissa’s per-lookup credit math.