You can ask your AI assistant for what you need in plain language. The examples show ways to phrase a request; the assistant chooses tools and fills their inputs from your request.
canvassed developer docs
canvassed MCP tools
See what canvassed MCP tools and prompts do, what they return, and how to ask for help.
To connect, sign in with a canvassed account that includes AI assistant access. Start a free 14-day trial, or add AI assistant access to Pro. You'll go straight back to your AI app once you're set up.
canvassed listings come from publicly available brokerage listing pages, and every listing links back to its source. Brokers can request an update or removal at info@canvassed.ai. Data sources and removal
Documentation artifact v1.2.38 · Updated November 5, 2026
How to use this
Listing search and details
Search listings
searchAvailableSearch listings from one natural-language query.
Search canvassed listings from a natural-language query. Results include listing IDs, page URLs, listing text, applied filters, and the listing columns used by those filters. `return_fields` requests additional supported fields and `exclude_fields` omits optional fields.
Example question and output
Example: “Find retail listings for lease in Austin.”
Role: Direct tool; it returns the requested information.
Choose this for a plain-language search when canvassed should extract common filters from one sentence.
What it needs: Include a city, state, county, or ZIP code in the query.
What you’ll see: Matching results with listing ID, title, URL, text, applied filters, and relevant listing fields.
Technical inputs
Search canvassed listings from a natural-language query. Results include listing IDs, page URLs, listing text, applied filters, and the listing columns used by those filters. `return_fields` requests additional supported fields and `exclude_fields` omits optional fields.
queryRequired- string
limit- integer · default:
10 return_fields- array
exclude_fields- array
Fetch a listing
fetchAvailableFetch a listing returned by search using its ID.
Retrieve a canvassed listing by its ID, including its public page details and available listing metadata.
Example question and output
Example: “Show details for listing ABC123.”
Role: Direct tool; it returns the requested information.
What you’ll see: The full safe listing record.
Technical inputs
Retrieve a canvassed listing by its ID, including its public page details and available listing metadata.
idRequired- string
Search listings with filters
search_listingsAvailableSearch commercial real estate listings with structured filters and optional semantic ranking.
Search listings using structured filters and optional semantic ranking over listing-page text. A geography filter is required in structured_filters, or a city, state, county, or ZIP code must appear in semantic_query. Always resolve vague place names first. If needs_clarification is true, ask the user to choose, then search again with the chosen ZIPs, city or radius. ZIP filters use geog_zip; exact point radii use within_radius with lat, lon, and miles, or an address of a geocoded listing. Use `zoning_code` with a Los Angeles County geography filter to match stored City of LA or Long Beach municipal, selected-jurisdiction SCAG regional, or County Z-NET zone codes linked to listing parcels. Request `return_fields=["zoning_code"]` to include parcel-derived zoning and its source in each result. Broker-stated zoning appears separately as listing text. When filters leave no semantic text, results are sorted by most recently updated. Compact responses are the default; use response_mode `standard` for up to three short snippets or `full` for complete evidence. Pass `keywords` for exact zoning, use, or feature phrases; known terms and quoted phrases are detected automatically. `keyword_mode="require"` limits results to text matches, and `keyword_hits` explains matches. Oversized responses include `truncated` and `next_offset` for paging. `return_fields` requests supported fields and `exclude_fields` omits fields.
Example question and output
Example: “Find retail listings in Los Angeles County with zoning code C2.”
Role: Direct tool; it returns the requested information.
Choose this when the request needs exact structured filters or semantic ranking over listing-page text.
What it needs: A geography filter is required. Use `geog_city`, `geog_county`, `geog_state`, or `geog_zip` in `structured_filters`, or include a city, state, county, or ZIP code in `semantic_query`.
What you’ll see: Matching listings with applied filters, pagination information, and relevant listing fields, including requested parcel zoning when available.
Technical inputs
Search listings using structured filters and optional semantic ranking over listing-page text. A geography filter is required in structured_filters, or a city, state, county, or ZIP code must appear in semantic_query. Always resolve vague place names first. If needs_clarification is true, ask the user to choose, then search again with the chosen ZIPs, city or radius. ZIP filters use geog_zip; exact point radii use within_radius with lat, lon, and miles, or an address of a geocoded listing. Use `zoning_code` with a Los Angeles County geography filter to match stored City of LA or Long Beach municipal, selected-jurisdiction SCAG regional, or County Z-NET zone codes linked to listing parcels. Request `return_fields=["zoning_code"]` to include parcel-derived zoning and its source in each result. Broker-stated zoning appears separately as listing text. When filters leave no semantic text, results are sorted by most recently updated. Compact responses are the default; use response_mode `standard` for up to three short snippets or `full` for complete evidence. Pass `keywords` for exact zoning, use, or feature phrases; known terms and quoted phrases are detected automatically. `keyword_mode="require"` limits results to text matches, and `keyword_hits` explains matches. Oversized responses include `truncated` and `next_offset` for paging. `return_fields` requests supported fields and `exclude_fields` omits fields.
semantic_query- string
keywords- array
keyword_mode- string · default:
boost structured_filters- object
return_fields- array
exclude_fields- array
response_mode- string · default:
compact structured_top_k- integer · default:
10000 chunk_top_k- integer · default:
200 listing_top_n- integer · default:
10 listing_offset- integer · default:
0 max_chunks_per_listing- integer · default:
3 min_supporting_chunks- integer · default:
2
Get a listing by ID
get_listing_by_idAvailableReturn one canonical listing record by listing ID.
Retrieve one canonical canvassed listing record by listing ID, including available attributes and dates.
Example question and output
Example: “Look up canvassed listing ABC123.”
Role: Direct tool; it returns the requested information.
What you’ll see: The listing record and whether it was found.
Technical inputs
Retrieve one canonical canvassed listing record by listing ID, including available attributes and dates.
listing_idRequired- string
Get parcels for a listing
get_listing_parcelsAvailableLook up County parcels and available County, municipal, and regional zoning linked to a canvassed listing.
Return all Regrid parcels matched to a listing and their linked LA County parcel APNs/AINs, County Z-NET zoning, City of LA or Long Beach municipal zoning, and (where available) separate SCAG regional zoning keyed by APN. The top-level zoning_code uses municipal, regional, then County precedence and includes its source. The response reports source vintages, parcel and zoning match status, and manual review flags. County parcel coverage is Los Angeles County; SCAG regional zoning covers selected incorporated jurisdictions.
Example question and output
Example: “Show the parcels and zoning for listing ABC123.”
Role: Direct tool; it returns the requested information.
What you’ll see: Regrid parcel identifiers, County APN/AIN and situs details, County Z-NET zoning, available City of LA or Long Beach zoning, SCAG local and standardized regional zone codes, the preferred top-level zone and its source, source vintages, match statuses, and manual-review flags.
Technical inputs
Return all Regrid parcels matched to a listing and their linked LA County parcel APNs/AINs, County Z-NET zoning, City of LA or Long Beach municipal zoning, and (where available) separate SCAG regional zoning keyed by APN. The top-level zoning_code uses municipal, regional, then County precedence and includes its source. The response reports source vintages, parcel and zoning match status, and manual review flags. County parcel coverage is Los Angeles County; SCAG regional zoning covers selected incorporated jurisdictions.
listing_idRequired- string
Listing contacts
Get listing contacts
get_listing_contactsAvailableReturn available broker or contact details for a listing.
Retrieve available broker or contact names, email addresses, valid US phone numbers, license details, and titles for a canvassed listing ID. Contact details are grouped by person only when listing data supports a unique match. Email addresses are normalized to lowercase; unmatched emails and phone numbers remain unassigned. Compatible MCP clients may display progress updates.
Example question and output
Example: “Who is the broker for listing ABC123?”
Role: Direct tool; it returns the requested information.
Choose this when broker contact details are needed for a listing; get_listing_by_id returns property details without those contacts.
What you’ll see: Available contact names, emails, US phone numbers, license details, and titles. Contact details are grouped by person only when listing data supports a unique match. Email addresses are normalized to lowercase; unmatched emails and phone numbers remain unassigned. Compatible MCP clients may show progress while the server checks listing data.
Technical inputs
Retrieve available broker or contact names, email addresses, valid US phone numbers, license details, and titles for a canvassed listing ID. Contact details are grouped by person only when listing data supports a unique match. Email addresses are normalized to lowercase; unmatched emails and phone numbers remain unassigned. Compatible MCP clients may display progress updates.
listing_idRequired- string
max_chunks- integer · default:
25
Geography, companies, and filters
Resolve a location
resolve_geographyAvailableResolve an ambiguous or approximate place into canonical listing filters.
Resolve a place name to approved area aliases, ZIPs, cities, counties, states, or radius filters. Always resolve vague place names first. If needs_clarification is true, ask the user to choose, then search again with the chosen ZIPs, city or radius. Ambiguous areas return concrete options; preserve partial_zips as approximate coverage, separate from full ZIP coverage.
Example question and output
Example: “Search around downtown Nashville within 20 miles.”
Role: Helper tool; it prepares or clarifies inputs for another tool.
What you’ll see: Matched geography and recommended search filters.
Technical inputs
Resolve a place name to approved area aliases, ZIPs, cities, counties, states, or radius filters. Always resolve vague place names first. If needs_clarification is true, ask the user to choose, then search again with the chosen ZIPs, city or radius. Ambiguous areas return concrete options; preserve partial_zips as approximate coverage, separate from full ZIP coverage.
queryRequired- string
radius_miles- number · default:
15 max_zip_list- integer · default:
100 max_city_list- integer · default:
15 expand_nearby- boolean · default:
true
Resolve a company
resolve_companyAvailableMatch a company or brokerage phrase to canonical company names.
Match a company or brokerage phrase to canonical company names found in canvassed listings. Results include ranked candidates.
Example question and output
Example: “Find the canonical name for CBRE.”
Role: Helper tool; it prepares or clarifies inputs for another tool.
Use this to identify the exact company name stored in canvassed before filtering or counting listings by company.
What you’ll see: Candidate company names from current listings.
Technical inputs
Match a company or brokerage phrase to canonical company names found in canvassed listings. Results include ranked candidates.
queryRequired- string
limit- integer · default:
5
List filter values
list_filter_valuesAvailableFind available values for a supported listing filter.
List values available for a supported listing filter field, optionally narrowed by a prefix.
Example question and output
Example: “Which property types are available?”
Role: Direct tool; it returns the requested information.
What you’ll see: Matching filter values and related metadata.
Technical inputs
List values available for a supported listing filter field, optionally narrowed by a prefix.
fieldRequired- string
prefix- string
limit- integer · default:
25
Counts and availability
Count listings
count_listingsAvailableCount listings matching filters, optionally grouped by one field.
Count listings that match structured filters, optionally grouped by a field, with compact sample records by default. A geography filter is required in structured_filters. Always resolve vague place names first. If needs_clarification is true, ask the user to choose, then search again with the chosen ZIPs, city or radius before counting. Use response_mode `standard` or `full` for more detail. Oversized samples include `truncated` and `next_offset` for paging.
Example question and output
Example: “How many retail listings for lease are in Austin?”
Role: Direct tool; it returns the requested information.
Choose this for totals or grouped counts instead of a list of matching listings.
What it needs: A geography filter is required in `structured_filters`.
What you’ll see: A total count, optional grouped counts, and sample listings.
Technical inputs
Count listings that match structured filters, optionally grouped by a field, with compact sample records by default. A geography filter is required in structured_filters. Always resolve vague place names first. If needs_clarification is true, ask the user to choose, then search again with the chosen ZIPs, city or radius before counting. Use response_mode `standard` or `full` for more detail. Oversized samples include `truncated` and `next_offset` for paging.
structured_filters- object
group_by- string
examples_limit- integer · default:
3 examples_offset- integer · default:
0 return_fields- array
exclude_fields- array
response_mode- string · default:
compact
History and market changes
Search listing changes
search_listing_changesAvailableReturn listing lifecycle events for a selected date window and optional filters.
Search listing-level added and removed events in a date window, with optional active-at-start context, listing filters, and cursor pagination. Event rows include the available 15 pt_* property-type flags in compact, standard, and full modes; response_mode `full` adds the remaining public event fields. Oversized pages are shortened at item boundaries and include a continuation cursor.
Example question and output
Example: “Show additions and removals in Travis County, Texas, during January 2026.”
Role: Direct tool; it returns the requested information.
What you’ll see: One page of change-log events with date-only valid_from and valid_to, no listing-level date_created, cleaned property_type labels, available pt_* property-type flags, event dates, listing identifiers, and a next cursor. Use response_mode=full for all other available public event fields.
Technical inputs
Search listing-level added and removed events in a date window, with optional active-at-start context, listing filters, and cursor pagination. Event rows include the available 15 pt_* property-type flags in compact, standard, and full modes; response_mode `full` adds the remaining public event fields. Oversized pages are shortened at item boundaries and include a continuation cursor.
start_dateRequired- string
end_dateRequired- string
filters- object
event_type- string · default:
all include_active- boolean · default:
false per_page- integer · default:
25 cursor- string
response_mode- string · default:
compact
Summarize listing changes
summarize_listing_changesAvailableReturn reconciled change-over-time totals, with optional group breakdowns.
Summarize listings active at the start and end of a date window and listing lifespans added or removed during it, optionally grouped by one or two dimensions. Set group_by=property_type for change counts by the available pt_* classifications; these groups can overlap.
Example question and output
Example: “Summarize listings added and removed in Manhattan during May 2026, grouped by property type.”
Role: Direct tool; it returns the requested information.
What you’ll see: Overall start-active, added, removed, end-active, net/gross change, rates, reconciliation, and optional grouped rows. Property-type groups are derived from available pt_* flags and can be non-additive.
Technical inputs
Summarize listings active at the start and end of a date window and listing lifespans added or removed during it, optionally grouped by one or two dimensions. Set group_by=property_type for change counts by the available pt_* classifications; these groups can overlap.
start_dateRequired- string
end_dateRequired- string
filters- object
group_by- string
Generate Change Over Time report
generate_change_over_time_reportAvailableCreate a human-readable market change report with summary metrics and detailed events.
Combine a Change Over Time summary with a cursor-paginated listing change log and format the result as a readable market change report. Set summary_group_by=property_type for summary counts by the available pt_* classifications; the formatted and spreadsheet summaries label the selected grouping.
Example question and output
Example: “Create a May 2026 market change report for Manhattan, with a summary by property type.”
Role: Direct tool; it returns the requested information.
What you’ll see: Formatted report text, JSON summary and event records with date-only validity fields, no listing-level date_created, cleaned property_type labels, and available pt_* property-type flags, plus source freshness and completeness/cursor metadata. Property-type group counts may overlap.
Technical inputs
Combine a Change Over Time summary with a cursor-paginated listing change log and format the result as a readable market change report. Set summary_group_by=property_type for summary counts by the available pt_* classifications; the formatted and spreadsheet summaries label the selected grouping.
start_dateRequired- string
end_dateRequired- string
filters- object
max_records- integer · default:
250 summary_group_by- string · default:
company
Export Change Over Time spreadsheet
export_change_over_time_spreadsheetAvailableGenerate a shareable Excel report for a selected date window and optional filters.
Export an Excel workbook with Report Summary and Change Log tabs for a selected market and date window. Set summary_group_by=property_type to include added/removed summary counts by the available pt_* flags.
Example question and output
Example: “Export the May 2026 Manhattan change-over-time report with a property-type summary.”
Role: Direct tool; it returns the requested information.
What you’ll see: An XLSX workbook with summary metrics by the selected grouping and a detailed change log with date-only validity fields, no listing-level date_created, cleaned property_type labels, and available pt_* property-type flags; property-type groups may overlap, and output includes completeness metadata when the record cap is reached.
Technical inputs
Export an Excel workbook with Report Summary and Change Log tabs for a selected market and date window. Set summary_group_by=property_type to include added/removed summary counts by the available pt_* flags.
start_dateRequired- string
end_dateRequired- string
filters- object
max_records- integer · default:
250 summary_group_by- string · default:
company
Help
canvassed help
helpAvailableExplain how to use canvassed tools, including the available Change Over Time tools.
Explain the available canvassed tools and workflows, including listing-change summaries and listing-level change outputs. It uses the published guide and does not query customer data.
Example question and output
Example: “How do I summarize listing changes?”
Role: Helper tool; it prepares or clarifies inputs for another tool.
What you’ll see: Readable Markdown help with the relevant tool, required inputs, expected output, and guide link.
Technical inputs
Explain the available canvassed tools and workflows, including listing-change summaries and listing-level change outputs. It uses the published guide and does not query customer data.
question- string
topic- string
tool_name- string
prompt_name- string
MCP prompts
canvassed help prompt
canvassed-helpAvailableSelectable shortcut for MCP clients that support prompts. It returns the same quick guide or topic-specific help as the Help tool.
Example and output
Example: “Select canvassed help and ask for troubleshooting.”
What you’ll see: One user-facing guide message; no topic returns the concise quick guide.
Prompt input
topic- string
canvassed MCP Help guide
Quick reference
The canvassed MCP server lets you ask an AI assistant to find and review commercial real estate listings. Describe the market, property type, and what you need in plain language; the assistant can use canvassed tools to search and explain the results.
Add canvassed as a custom connector in your AI app. Once canvassed is listed in your AI app’s directory, you can connect from there instead.
- “Find retail listings for lease in Austin.”
- “Show me industrial listings under 50,000 square feet in Phoenix, AZ.”
- “Which brokerages have the most multifamily listings in LA County?”
- “Who is the broker for listing ABC123?”
- “Show the parcels and zoning for listing ABC123.”
- “What can I filter listings by?”
For help, ask a question in plain language, name a tool, or ask for a topic such as setup, tips, troubleshooting, or recent changes. Read the setup guide or tool reference.
Welcome
The canvassed MCP server connects canvassed listing and analysis tools to an AI assistant. You can ask in everyday language, and the assistant chooses the tools that fit your request.
Get started
To connect and try the canvassed MCP server:
- In Claude, open Settings → Connectors → Add custom connector and enter
https://mcp.canvassed.ai/mcp. In other AI apps, follow the canvassed setup guide. - When your AI app asks, sign in to your canvassed account and approve the connection. The MCP uses your account sign-in, not an API key.
- Ask for a listing search or analysis in plain language.
- Refine the request with a location, property type, price, size, or other detail.
canvassed works with a canvassed account that includes AI assistant access. Sign in when your AI app asks. Setup: https://www.canvassed.ai/developers/mcp/onboarding
Once canvassed is listed in your AI app’s directory, you can connect from there instead.
How to
Find listings
- Ask for a property type, location, and sale or lease preference.
- Add price, size, or other filters when you have them.
- Parcel and zoning lookups currently cover Los Angeles County, California. Add a Los Angeles County city or ZIP filter and
zoning_codeto search listings by zoning; it matches stored County Z-NET, Long Beach municipal, and selected-jurisdiction SCAG zone codes linked to a parcel. - Add
return_fields=["zoning_code"]to include parcel zoning and its source in search results. If a query becomes filters with no semantic text left, results are sorted by most recently updated listing. - Search results use compact responses by default. Use
response_mode="standard"for a few short snippets or"full"for complete evidence; large responses may include a continuation offset. - For exact zoning, use, or feature language, pass the key phrase in
keywords. Known glossary terms and quoted phrases are detected fromsemantic_query;keyword_mode="require"keeps only listings whose text contains a match.
Review changes over time
- Give a start date and an end date; the end date is exclusive. For example, June through August uses
2026-06-01and2026-09-01. - Add a market or listing filter such as a county FIPS code, company, property type, or transaction type. Omitting geography searches nationally.
- Use
summarize_listing_changesfor totals,search_listing_changesfor listing-level added and removed events,generate_change_over_time_reportfor a readable report, orexport_change_over_time_spreadsheetfor an Excel workbook.
Clarify a location
- Describe the place or area you have in mind. Recognized aliases can resolve to ZIPs, cities, or counties.
- If the area is vague or could mean more than one market, the assistant asks whether to use specific ZIPs, cities, or a radius around an address or point. It confirms your choice before searching and does not silently expand to a county or state.
- For an exact radius, provide a center and distance in miles. A ZIP or city area uses its available listings; it is not an exact neighborhood boundary.
Parcel and zoning
Use get_listing_parcels with a listing ID to see its matched Regrid parcels, linked County APNs/AINs, and available zoning. Each parcel preserves County Z-NET, municipal, and SCAG regional fields separately. The top-level zoning_code uses the best available source in this order: municipal, SCAG regional, then County Z-NET; zoning_source identifies that value. Municipal zoning is currently available for Long Beach and City of Los Angeles. SCAG zoning is available for selected jurisdictions, including Los Angeles, Long Beach, South Bay cities, and the LA County side of the Conejo Valley. Match statuses, source vintages, all intersecting zones, and source-specific review flags are included. County Z-NET misses are not treated as zoning review issues for parcels in incorporated cities. Secondary intersecting zones trigger review only when they cover more than 10% of the parcel. Listing search keeps broker-stated zoning text separate from parcel-derived zoning and its source.
For example, ask “Find retail listings in Los Angeles County with zoning code C2,” or “Show the parcels and zoning for listing ABC123.”
Change over time
For a selected date range and market, summarize_listing_changes returns overall active-at-start, added, removed, and active-at-end totals, with optional groupings.
Use search_listing_changes for the listing change log, generate_change_over_time_report for a formatted report, and export_change_over_time_spreadsheet for an Excel workbook.
These tools report listing additions and removals; they do not provide a price-change timeline.
For a complete validity-interval history export, use the separate Data API GET /api/v1/data/listings/history endpoint. It returns date-only valid_from and valid_to, preserves null for open intervals, omits listing-level date_created, and includes the available pt_* flags. It uses an API-Key; MCP sign-in does not substitute for a Data API key.
Tips for better results
- Include a city or area and the property type when you know them.
- Use compact listing responses by default. Request
response_mode="standard"for up to three short text snippets or"full"for complete listing evidence. Results without a semantic text query omit evidence. - For a key zoning, use, or feature term, provide
keywordsto boost literal text matches. Addkeyword_mode="require"when results must contain one of those terms; checkkeyword_hitsfor the matched phrase. - State whether you want properties for sale or lease.
- Give ranges and units for price, size, and drive time. Search results include the columns used by filters; use
return_fieldsto request other supported fields orexclude_fieldsto omit optional fields. - Say when you want exact boundaries or nearby areas included.
- Use
resolve_geographyfor neighborhood nicknames or corridor descriptions. When it returns clarification options, choose the ZIPs, city, or radius that best matches the area, then search again with that choice. Keeppartial_zipsseparate from full-coverage ZIPs. geog_zipaccepts one ZIP or a list.within_radiusaccepts{ "lat": 34.0, "lon": -118.0, "miles": 5 }, or{ "address": "an exact geocoded listing address", "miles": 5 }.- Ask one follow-up at a time if you want to narrow results.
What you can do
Some tools return results directly. Others help the assistant clarify a request or prepare a search. Results use the tools available to your account. Help itself returns documentation and does not query listings.
| Ask for | Example | What you get |
|---|---|---|
| Listings | “Find retail for lease in Austin.” | Matching listings and details |
| Counts and filters | “Count listings by property type.” | Counts or available filter values |
| Market changes | “Summarize May listing changes for Manhattan.” | Active-at-start, added, removed, and active-at-end totals, with optional groupings |
| Listing details | “Show details for listing ABC123.” | Listing information, plus contact names, emails, US phone numbers, and available license details when you ask |
| Parcel and zoning lookup | “Show the parcels and zoning for listing ABC123.” | Regrid parcel identifiers, linked County APN/AIN and situs details, County Z-NET zoning, Long Beach municipal zoning, selected-jurisdiction SCAG regional zoning, source vintages, match statuses, and manual-review flags |
| Help | “What can canvassed do?” | A short answer or a link to more detail |
See the canvassed tool reference for current tool names and details.
Tools reference
canvassed includes listing search, listing lookup, parcel and zoning lookup, counts, geography and company lookup, listing-change summaries, and contacts. Parcel and County Z-NET coverage includes Los Angeles County, California. Municipal zoning is currently available for Long Beach and City of Los Angeles; SCAG regional zoning covers selected incorporated jurisdictions. The online tool reference lists each available tool, its inputs, and examples.
Compatible MCP clients can fetch the full guide from the canvassed://help resource. Fetching the resource does not guarantee that a client will display it in chat automatically.
Plans and help
Help cannot create accounts, change permissions, issue API keys, or look up billing details. Contact canvassed for account or product questions.
Guide details
Guide version 1.2.38 · Last updated 2026-11-05
Documentation: MCP setup · MCP tools · Developer docs · API reference
Robots and AI crawler access
The public canvassed website uses robots.txt to allow search engines and AI crawlers to read public marketing and developer pages while asking them not to crawl app and data routes. This helps partners and users find public canvassed information; it does not expose account data or authorize access. Robots rules are crawler guidance, not security controls. Sign-in and backend authorization continue to protect listing data and MCP access.
Troubleshooting
| If this happens | Try this |
|---|---|
| A location is unclear | Add a city, state, ZIP code, or nearby landmark. |
| A neighborhood or corridor needs clarification | Choose the ZIPs, cities, or radius that best matches the area. The search waits for that choice instead of widening to a county. |
| No listings match | Broaden the area or remove a filter. |
| A search asks for a location | Add a city, state, county, or ZIP code. |
| A change-over-time request reports that its source is unavailable | Try a narrower market or simpler grouping once. If it keeps failing, contact canvassed with the dates and filters. |
| A contact lookup takes time or fails | Compatible AI clients may show progress while canvassed checks the listing data. If it fails, try once later; if the issue continues, contact canvassed and include the listing ID and error text. |
| A company is missing | Try its full brokerage name with resolve_company; contact canvassed if you believe its listings are missing. |
| You cannot connect | Follow the setup guide for your AI app. |
| You cannot find canvassed in Claude's connector directory | Add it as a custom connector using the setup guide. Once canvassed is listed in your AI app’s directory, you can connect from there instead. |
Help cannot diagnose a specific service incident, show live service status, or change account settings. Contact canvassed for current service or account issues.
Recent changes
- November 5, 2026: Clarified custom connector setup and access wording, routed sign-in questions to Get started, corrected tool descriptions, and aligned the public name as canvassed.
- November 3, 2026: Contact lookup normalizes email addresses to lowercase and associates an email with a person only when the name match is unique. Unmatched emails remain available without a person assignment.
- November 2, 2026: Claude users can add canvassed as a custom connector; the guide explains how to connect before directory listing.
- October 21, 2026: Parcel lookup selects top-level zoning from municipal, SCAG regional, then County Z-NET sources and identifies its source. Clean municipal matches with at least 98% parcel coverage do not trigger aggregate zoning review. City of Los Angeles municipal zoning is available alongside Long Beach.
- October 21, 2026: Geography resolution can use an editable alias library, request clarification for vague areas, and filter by ZIP or exact radius.
- October 21, 2026: Listing search responses are compact by default; use
standardorfullfor additional detail.