Bedrooms
2
Exact value has a dated official-source observation.
property.beds
Loading
Connect a compatible assistant through MCP, or call the same tools from your software. These prompts are ready to adapt; bracketed details are yours to supply.
Choose your setup path →Interactive example · Fictional data
Choose a field to see its value, qualifications and matching reference. This is a saved synthetic packet, not a live property lookup. Every date and address below belongs to the example. No account or API answer is used.
2
Exact value has a dated official-source observation.
property.beds
ref_35b0c0972c8897da733171c4
A matched address is an identity check. It does not certify the building facts. An observation date belongs to its referenced subject; it cannot date a different field. The packet generation time is not a source observation.
The following notice strings are copied from the synthetic test fixture, not publisher permissions or endorsements:
01
Use this before a listing conversation. The packet brings together available facts and the questions still worth asking.
Research this Washington property: [county and parcel ID, or full address including unit and ZIP]. Use wa_research_packet with compact output. Explain how the property matched. Separate reported facts from calculations and unknowns. Match each citation to that exact property, field and source; a permit observation date does not establish when an assessor fact was observed. Preserve each field's stale, unverified or observed qualification, source dates and required attributions. Do not treat permit descriptions as verified current property characteristics.
What to check: A matching explanation, referenced facts, visible gaps and follow-up questions. If the match is ambiguous, the assistant should ask for the missing identity details.
POST /api/v1/agent-api/v1/research-packet
02
Captured history is still being established. A property can have current permit observations but no preserved versions yet. Choose a time window; Sentinel returns the versions it actually captured.
Use wa_property_changes for [county and parcel ID]. Show changes since [ISO date and time with timezone]. Separate corrected fields from agency republication and from reported permit event dates. State when immutable history starts and whether more pages remain. If history is unavailable, say so; do not infer that no changes or permits exist.
What to check: A bounded record of captured changes. Initial captures are baselines, not new work. Historical views are available only from the first captured version.
POST /api/v1/agent-api/v1/property-changes
03
Use this to prepare a seller discussion. These are supplied scenarios, not valuations or comparable sales.
Use wa_compare_seller_scenarios for King County. Compare a $750,000 sale with $0 seller credits against an $800,000 sale with $5,000 seller credits. Use 5% total commission as an explicit negotiable assumption. Mortgage payoff is unknown: omit it. Show the labeled amounts before payoff and any remaining assumptions. Do not present final take-home proceeds or a confirmed difference when the tool says they are not comparable.
What to check: The missing payoff remains unknown. The answer explains the basis of the calculated amounts and the inputs needed for confirmed proceeds.
POST /api/v1/agent-api/v1/seller-scenarios
Download the n8n workflow, server-side Python client and setup guide. The included property request is synthetic: replace it with the complete property identity before calling Sentinel. Store your key in the workflow credential manager or your server environment.
Download the integration starter →The starter preserves the response and its required notices. The n8n workflow was tested by isolated import, with no credentials or execution; the Python transport was tested offline. Your configured integration still needs a trial run.