Higher rate limits, bulk county downloads, and a named SLA contact — the same data the free site runs, without the community ceiling.
UrbanKit Studio indexes the parcel REST endpoints of 128 US counties and turns them into working tools. The public site is free and stays free. This page is for the teams who moved past evaluating and now run the data in production: proptech platforms, title and escrow shops, land-use lawyers, and the GIS consultants who serve them.
The same address-to-APN and county-query engine the free tools run on, with rate limits raised for production traffic instead of the community ceiling.
Pull a whole county, or a whole state, as JSON or CSV. No paging through ten thousand records to assemble what you already know you need.
The public-notice mailing tool with seats for your staff. Buffer a parcel, capture every owner in the ring, export Avery-ready labels.
An uptime commitment and a named contact who knows your account, so a broken county endpoint is our problem to chase, not yours.
Ranges, not checkout prices. We scope the quota and the SLA to what you run, then send an invoice. No card on file, no Stripe redirect, no surprise overage bill.
The atlas, the browser tools, and the MCP server stay free. Evaluate the data on real addresses before you talk to anyone.
For a single team that hits the public tier's ceiling. Higher API rate limits and bulk county exports you can schedule.
For proptech, title, land-use, and GIS shops that depend on this in production. Volume, an SLA, and someone who answers the phone.
Point an AI agent at the MCP server, or install the SDK and resolve a few addresses in the counties you work. The free tier covers an honest evaluation.
Access. The data and the tools are the same ones the free site exposes; a paid plan removes the community rate limit on the Parcel Data API, lets you pull whole counties as JSON or CSV instead of paging through them, and gives your team seats on the radius-notice tool. Enterprise plans add an uptime SLA and a named contact.
County and municipal ArcGIS REST endpoints, the same public sources a county GIS analyst would query. The atlas indexes 128 counties with verified endpoints and field metadata. We do not resell a third party's database; we index the authoritative public layers and keep them current.
Because the right number for a title shop pulling two counties is not the right number for a proptech platform hitting the API a million times a month. We scope the quota and the SLA to what you run; a rate card that fits nobody isn't a rate card. Self-serve billing is on the roadmap; the deals that close today close on a call and an invoice.
Those vendors sell a normalized national parcel database with their own schema and their own license. UrbanKit indexes the public county REST endpoints directly, so you query each county the way its assessor stored it, with the original field names. If you need the assessor's source record for specific counties, that is the fit; if you need a smoothed national layer for portfolio screening, a vendor like Regrid is the right call.
Yes, and you should. Wire the MCP server into Claude or Cursor, or install the npm SDK, and run it against the counties you care about. The free tier is enough to prove the data fits your workflow. When you outgrow the community rate limit, that is the signal a plan pays for itself.