Nebraska reCAPTCHA v2 — the $0.003 lookup floor

When you pull a business record from Nebraska’s Secretary of State, you hit a CAPTCHA before the data appears. That gate costs money to pass through at scale. Understanding that friction point matters if you’re pricing verification work or deciding whether to verify every applicant or a subset.

Why Nebraska locked the gate

Most state business registries are simple HTML forms. Search, get results. Nebraska’s system requires solving a CAPTCHA before you can query it. The state uses Google’s reCAPTCHA v2 (the “I’m not a robot” checkbox variant), which is cheap for humans to solve once per session but creates a cost floor for automated lookups.

This isn’t paranoia on Nebraska’s part. Secretary of State databases are high-value targets for scrapers, credential-stuffing bots, and people building parallel business registries. The CAPTCHA raises the friction cost enough to slow casual abuse without blocking legitimate users. The downside is that anyone doing systematic verification · bankers, equipment finance shops, credit underwriters · has to solve it programmatically or work around it manually.

The per-lookup math

Third-party CAPTCHA-solving services (2Captcha, Anti-Captcha, others) will solve a reCAPTCHA v2 for roughly $0.003 per solve. That’s not expensive in absolute terms. But it adds up. If you’re verifying 100 applicants a month, that’s $0.30. If you’re an equipment-finance lender running 5,000 lookups a month, that’s $15. Add other states with similar gates, and you’re looking at a meaningful line item.

The cost isn’t a bug · it’s intentional friction. Nebraska is saying: if you want to query us at volume, you’re paying the solve fee. The state gets protection; you get a price floor per lookup.

What you’re really verifying

The Nebraska Secretary of State database contains formation records, amendments, good-standing status, registered agent, and officer names. For underwriting, that means you can confirm the entity exists, who filed it, and whether it’s currently active. You cannot see UCC filings from the registry itself (those live in county clerk records, separately). You cannot see beneficial-owner disclosure forms (those are in a different system, and Nebraska does not require them for all entity types).

The CAPTCHA solves only the access problem. What you do with the data once you have it is the real work. An entity that passes the Nebraska lookup can still be a shell, a fraud, or months away from delinquency.

Integrating the cost into pricing

If you’re a broker or fintech offering verification, the $0.003 per Nebraska lookup is a real cost you cannot avoid. You have three options.

First, fold it into a flat verification fee and accept that Nebraska adds a small margin loss per transaction. Second, quote a higher fee when you know Nebraska is in scope. Third, do Nebraska only on request, not for every applicant. Most firms doing high-volume equipment finance choose option one · the per-lookup cost is small enough that bundling it into a $50–$150 verification report makes sense.

If you’re an underwriter doing this yourself, the CAPTCHA is just friction. It adds 10–15 seconds per lookup if you’re hand-solving, or a few milliseconds if you’re using a solve service and automation. The real cost is your time or your outsourcing dollars.

Other states with similar gates

Nebraska is not alone. A handful of other states use CAPTCHAs or equivalent bot gates on their business registries. Some are easier to work around; some are harder. The common denominator is that none of them are free to bypass at scale. The moment you move to systematic verification across 50 states, you’re budgeting for multiple solve points.

The gate is getting more common, not less. States are increasingly aware that uncontrolled scraping damages their databases and the registries’ integrity. Expect more CAPTCHAs, not fewer.

Bottom line

Nebraska’s reCAPTCHA v2 adds $0.003 per lookup, no way around it. That’s low enough that most underwriters fold it into the cost of doing business. The real lesson is that at-scale verification requires budgeting for friction points across multiple states. Build that into your pricing, timeline, and process assumptions. If you’re verifying Nebraska applicants one at a time by hand, the CAPTCHA is an annoyance. If you’re doing it at volume, it’s a line item.