Homies Stats
Canadian housing markets, prices, sales, inventory and economic history. Every result keeps its source, dates and units.
Explore the dataGive your agent market statistics, paperwork and property search through one account connection. Build home evaluations, market reports and tailored buyer lists.
The setup button copies a complete request for your agent. No URLs or placeholders to edit.
One key. Three toolsets.
16 MCP tools · 71 REST operations
Individual account authentication
Canadian housing markets, prices, sales, inventory and economic history. Every result keeps its source, dates and units.
Explore the dataDiscover forms, validate transaction details and prepare offers and other real estate documents using your account’s permitted library.
Explore paperworkSearch U.S. sale, rental, pending and sold listings through HomeHarvest. Licensed IDX and DDF access requires your own feed permissions.
See listing accessConnector technical specs
Choose the connection type used by your connector, then copy the matching fields. This page is the public documentation URL; requests run against the API endpoint below. Submission and directory approval are separate from having a working endpoint.
Choose MCP in the connector form and use the Streamable HTTP endpoint below. The OpenAPI link is an optional reference for the companion REST API.
MCP (Streamable HTTP)
A Homies account and an individual Homies API key are required. Existing Homies Paperwork account keys are supported. Store the key in the connector's secure credential settings and send it in the Authorization Bearer header. Each user connects their own account; access and usage limits apply per account. Paperwork availability depends on the user's jurisdiction, account permissions and applicable form-publisher terms. Generated documents are unsigned drafts that require review. Licensed listing feeds require the user's own authorized IDX connection through chat.homiesai.com or their own DDF credentials supplied through a secure onboarding process. Availability depends on the user's board, region, provider and data permissions. IDX/DDF credentials are separate from the Homies API key and must not be entered in this submission form. Current gateway coverage: Canadian market statistics and U.S. property search through HomeHarvest. Licensed IDX/DDF feeds are not yet connected to the unified API; Canadian listing search is not currently enabled. Canadian home evaluations require authorized sold comparables supplied by the user. Buyer-list tools prepare matches and unsent email drafts. Recurring delivery requires a separately configured persistent host runner, an authorized mailbox, recipient and schedule. No client delivery schedule is activated by connecting the API. OAuth with PKCE is not implemented in this release.
API keys
Select API keys in the authentication field. Use the Authorization header with the Bearer scheme. Leave OAuth with PKCE unselected for this release. Never put a key in a URL, prompt or submission note.
Use a natural request. Your agent collects the address, market or buyer criteria as needed, then uses the same workflow through REST or MCP.
01
Combine property facts, qualifying sold comparables and market context into an indicative evaluation for review. Canadian evaluations need supplied, authorized sold comparables.
evaluate_home
POST /v1/workflows/home-evaluation
02
Discover a supported Canadian geography and create a sourced report that preserves each metric’s actual period and any data gaps.
create_market_report
GET /v1/workflows/market-report
03
Match buyer criteria, explain the shortlist and prepare an email draft. The optional host runner adds recurring delivery after the sender, recipient and schedule are authorized.
prepare_buyer_list
POST /v1/workflows/buyer-list
Paperwork starts with list_forms and get_deal_schema, followed by validation and a reviewable draft. Read the buyer automation setup guide for schedules, sender authorization, duplicate prevention and delivery controls.
Connecting Homies does not grant access to someone else’s listing feed or licensed forms.
Use your existing Homies Paperwork key, or create an account. Store the key in your agent’s secure credential settings. Each protected request is validated against your account.
For licensed listings, sign in to your IDX through chat.homiesai.com, or supply your own authorized DDF keys through secure onboarding arranged with Homies. Feed credentials are separate from your Homies key. Do not send either in a prompt or the Muse review form.
The unified API currently serves Canadian statistics and U.S. HomeHarvest listings. IDX/DDF feeds are not yet connected to this gateway. Canadian listing search remains unavailable until that integration is enabled; Canadian evaluations can use supplied, authorized sold comparables.
Forms depend on publisher permissions and remain unsigned drafts. Buyer tools prepare unsent email drafts. Sending, signing and other external actions require the relevant authorization and connected service.
Use the live specification for request and response schemas. Discover geography and form IDs before calling a workflow. Keep sources, observation dates, coverage warnings and review requirements in the result.
Missing or invalid keys return 401. Respect rate limits and any Retry-After response. A healthy process does not guarantee every upstream source is available.
Documentation reviewed September 19, 2026 · Gateway v0.2.0. Check live capabilities for current coverage.
Agent setup guide · API privacy & access
Need the full product? Open Homies.
After authenticating and initializing the MCP connection, use tools/list to discover each tool’s current argument schema and annotations. The names below are exact; ? marks an optional argument. Structured search and request objects use the discovered schema. REST request and response schemas are in the linked OpenAPI reference.
search_geographiesReadArguments: query?
get_housing_seriesReadArguments: geography, series?, start?, end?
get_market_overviewReadArguments: geography
get_stats_catalogReadArguments: dataset?
get_stats_seriesReadArguments: dataset, series, geography?
search_propertiesReadArguments: search
list_formsReadArguments: jurisdiction?, board?
get_form_fieldsReadArguments: form_id, page?
get_deal_schemaReadArguments: section?
validate_paperworkRead / validateArguments: request
draft_paperworkWriteArguments: request
create_market_reportRead / prepareArguments: geography
evaluate_homeRead / prepareArguments: request
prepare_buyer_listRead / prepareArguments: request
list_paperwork_operationsReadArguments: none
paperwork_operationRead or writeArguments: method, path, body?, query?, idempotency_key?
error object. MCP tool failures set isError: true; inspect the error content and structured result. HTTP 200 or a completed tool call does not prove a transaction or workflow succeeded: inspect valid, draftable and job.status where returned.Idempotency-Key header for POST requests to /v1/paperwork/tools/*, /v1/paperwork/jobs and /v1/paperwork/schedules. For MCP, supply the same value as paperwork_operation.idempotency_key. Keys must be 8–120 printable non-space ASCII characters. Reuse a key only for retries of the same logical operation.Retry-After when returned. The gateway does not automatically retry mutating paperwork requests.paperwork_operation may send, publish, delete or accept publisher terms. Obtain the user’s explicit authorization for the applicable action and preserve account and publisher restrictions. A terms-required error remains blocking until the user has reviewed and accepted the returned terms; never accept them automatically to retry a draft.list_paperwork_operations for the MCP operation. Its paths start with /v1/; the corresponding public REST paths start with /v1/paperwork/. Keep account and feed credentials in secure host settings, outside tool arguments.