Read the ordinance, not the summary
Research agents open the governing code for a parcel and return the envelope it can legally hold, with every constraint cited to the section it came from.
Every constraint traced to a section
Base district, overlays, setbacks, height limits, parking ratios and fee schedules are read in place. Nothing is carried over from a neighbouring parcel or a summary table that stopped being current two amendments ago.
01
Ordinance reading
Agents work through the code text itself, including the amendments and conditional exceptions that summary tables quietly drop.
02
Overlay stacking
Corridor, historic and transit overlays apply in the order the jurisdiction applies them, so the limit you underwrite to is the binding one.
03
Fee schedules
Impact fees, exactions and in-lieu payments resolve to a per-unit figure that flows directly into the development budget.
How it works
From parcel to buildable envelope
-
01
Point at the parcel
An address or an APN is enough. Cayda resolves the jurisdiction, the governing code volume, and the effective date before it reads a word.
-
02
Agents read the code
Each constraint is pulled from its own section rather than a digest, then reconciled against overlays and any conditional use that changes the answer.
-
03
Get the buildable envelope
You get unit count, buildable area, required parking, and the fee load, each one clickable back to the ordinance that produced it.
The trail stays attached
Zoning findings do not stop at the research tab. They follow the number into the budget, so a figure in the pro forma can be walked back to the ordinance without leaving the model.
Waitlist
Join the waitlist
Developers and acquisition teams get access as new markets come online each week.