Use CrossBeam from Claude, ChatGPT or Copilot

How do I look up a city's rules, requirements and fees with Claude?

Where: Connect CrossBeam in Settings → AI Connectors, then ask Claude your permit question with the city

How do I look up a city's rules, requirements and fees with Claude?

Quick answer: With CrossBeam connected, ask Claude in plain words and name the city: "What will the permit fees be for an 800 sq ft ADU in Anaheim?", "What does Hermosa Beach want me to submit for a reroof?", or "What zone is 123 Main St in?" You don't need a project or a plan set, and none of it spends review credits.

Steps

  1. Connect CrossBeam to Claude. See Connect CrossBeam to Claude.
  2. Ask your question with the city, and the address if you have one.
  3. For fees, give the size or the valuation. Claude may ask a follow-up, such as the construction type, to price more lines.
  4. Read where each answer comes from. Fee lines cite the city's fee resolution; parcel facts name their source; code answers list the sections they looked up.
  5. Ask a follow-up in the same conversation. Claude keeps the thread, so you don't repeat yourself.

What each kind of question gets

You askYou get
Zoning, coastal, fire or flood zone for a lotThe parcel's site facts, each with its source
What to submit and how to package itThe city's checklist for that permit, or a clear note that CrossBeam only has the state minimum
A setback or window size to drawThe rule value with its citation. See Draw a permit set with Claude
Permit feesAn estimate from the city's adopted fee schedule. Fees set at intake are named but not priced.
Anything else about permits or codeAn answer from CrossBeam's permit assistant, the same one as Chat in the app

Good to know

  • A fee estimate is not a quote. The city confirms fees at intake.
  • When CrossBeam has no data for a city, it says so. That means unknown, not "nothing required": check with the city.
  • Code questions count toward your daily Chat limit.

Related

From an AI assistantfor Claude and other assistants connected to CrossBeam

Pick the narrowest tool:

  • Parcel facts: crossbeam_get_site_facts with address (or apn plus the city in address).
  • Submittal checklist: crossbeam_get_review_requirements with city and permit_type; lane for the document text (page with offset), packaging: true for packaging rules. The text covers several cases and says how to pick one; it does not pick for you.
  • Drawing limits: crossbeam_rules (see Draw a permit set with Claude).
  • Fees: crossbeam_fees with city, permit_type, and valuation or new_floor_area_sqft; optional adu_sqft, occupancy, stories, new_dwelling_units, scopes. Fee questions in the answer name what would price more lines; ask the person, then call again. planning_fee alone looks up one Planning application fee. The same estimate is JSON in structuredContent.estimate.
  • Open questions: crossbeam_ask with question, city (or state), permit_type, facts. Keep conversation_id for follow-ups and never resend earlier turns. status: "answering" means call crossbeam_get_conversation about 30 seconds later; do not ask again.

Watch for:

  • coverage: "none" means unknown. state_baseline is the state floor, not the city's list. With ask_instead, ask that question with crossbeam_ask instead of presenting the floor as the city's list.
  • Fees set at intake have no amount; keep them out of any subtotal.
  • A section the answer cites that is not in citations is unverified. Keep CrossBeam's answer apart from your own knowledge, and state law apart from a city amendment.
  • crossbeam_ask errors are structured: rate_limited (with resets_at), turn_in_progress, project_not_found, program_only. A failed turn is an error, never an empty answer.

Related

How do I look up a city's rules, requirements and fees with Claude? · CrossBeam Permits Help