cf0 Zero

Stores files that the user attached in the chat on one home in cf0. home is the draft_id, the home_id of a unit or a layout id from an earlier answer. Each file is a download_url, or file_base64 with mime_type and file_name. Without files, the result is upload_in_cf0 with the cf0 link where the signed-in user uploads that kind of file for that home. kind photos takes up to 20 photos, with an optional room for each photo and owner_has_photo_rights true, which records that the owner has the right to use the photos. remove_photo_ids removes photos of a home, and set_rooms changes the room of photos, by the photo ids that ask_agent gives for each home. kind floor_plan takes one floor plan as a PDF or an image, and on a unit cf0 starts the 3D plan build from it. kind ownership_proof takes one document (a PDF can have many pages) with proof_kind, and cf0 checks the proof by hand before the home can list. cf0 reads each file from its download_url or its base64 text, accepts JPEG, PNG, WebP and HEIC images up to 15 MB and PDF files up to 20 MB, and removes photo metadata. A Content-Type with parameters, such as application/pdf; qs=0.001, counts as its media type. A staged draft becomes a home first, which needs its rent and deposit. Otherwise the result is needs_rent. The result gives the number of stored files, each refused file with its reason, and the listing steps that the home still needs before it can list. After cf0 holds an ownership proof, the next step says that cf0 checks it by hand. It never lists or publishes a home.

add_home_files

Records the user's decision on an item that Zero waits on. The tool takes the item id and the version code from Zero's latest answer. It acts only on that version of the item. The user can approve or decline an action that Zero proposed. Only a member of the firm can decide on actions, and when the firm named approvers in Setup, only they can. The preview in ask_agent shows the recipient's role, the property, the send time in the firm's time zone and the full message. Other actions can be approved here after that preview. Some items are decided only in cf0: messages to 10 or more people, messages with sensitive content such as an access code, a phone number or an email address, email replies, actions too long to show in full, and a viewing change that Zero cannot name. For these items, the result gives the reason and a link to cf0. Zero sends an approved email within 10 minutes, after the email passes its send checks. Only the firm's named approver can approve, decline, unlist or relist a home. unlist takes a listed home off cf0, and relist lists an unlisted home again, with the version of the home from ask_agent. The listing_preview of a home in ask_agent shows what an approval of that version lists. A tenant item is a letting outcome. approve confirms that the home is let, and the letting fee becomes due under the terms that the firm accepted. decline voids the outcome. The user can answer a question from Zero with approve (yes), decline (no) or change, with their own answer in message. After the user answers a question, Zero writes its reply to the person, and the reply waits for approval. The user can also cancel a task. A cancelled task stops every email that Zero did not start to send. The result also tells when the item changed or when the user cannot decide it.

answer_agent

Reads the work of Zero, the AI property manager of the user's firm in cf0, for questions about that work. Examples are what Zero does now, what waits on the user and where a task stands. The tool only reads. It changes nothing and contacts no one. It returns Zero's answer, tasks from Zero's board and the items that wait on the user. Each action to approve has a preview. The preview gives the recipient's role and reference code, the property, the send time in the firm's time zone and the full message. An item that only cf0 can decide has a summary and a link to cf0, without the message. Each question from Zero is about a task that the user gave Zero. People on the firm's records appear as reference codes (p_…) with their role. A name that is not on the records appears as written. Email addresses, phone numbers and access codes are not in the result. Each item has an id and a version code, which answer_agent takes. New work for Zero goes to give_agent_task, also when the user says "ask Zero to …" or "get Zero to …". For lettings, it also gives the user's homes on cf0, with the status, the next step and the criteria that each home still needs before it can list. The answer text names each home with its status and next step, also when Zero setup is incomplete. Each home on cf0 has a preview, and each home that waits for approval has a listing_preview. The preview gives the address, the layout, the photo state and the confirmed facts that an approval of that version covers. With market set, it gives what the firm needs to list a home in that market. Each unit home has a version code for answer_agent and its layout_id. renters gives up to 10 of the newest enquiries and viewings for the user's homes, and next_renters_cursor gives the next page for renters_cursor. Each renter has the display name, the home, the enquiry stage, and for a viewing the time in the firm's time zone, the mode and the status. A viewing with an AI-guide report has a short guide_report. Contact details are not in the result. The id of an enquiry or a viewing goes to manage_renter. A letting outcome that waits for confirmation is an item in waiting_on_you.

ask_agent

Gives Zero new work with one person. This includes requests worded "ask Zero to …" or "get Zero to …". The work does not need to be on Zero's board first. Examples are access with a tenant for a repair, a check-out time with a guest, booked work for an owner, renewal terms for a tenant, or a reminder of late rent. Zero takes maintenance and access, move-out and turnover, owner updates, stay operations, leasing work with applicants, enquirers and renewing tenants on the firm's records, and reminders of late, missed or partly paid rent to current tenants. Zero does not take leads, cold outreach to people with no relationship with the firm, marketing, tenant screening checks, payments or card and bank details, legal or formal notices, or emergencies. people holds that one person: a name on the firm's records, or a role such as "tenant" with property set to the property. Zero does not take a phone number. Zero plans the task and writes one email from the firm's Zero address. Zero sends the email only after a person at the firm approves it, in cf0 or with answer_agent. An accepted result has the task id, Zero's plan and a link to the task in cf0. The same task on the same UTC day returns the first task while it is open. new_person holds the name, email, role and property of a person who is not on the firm's records. The first call with new_person adds no one and returns confirm_person with a confirm_code. A second call with the same task, new_person and confirm_code adds the person and gives Zero the task. Leasing work and rent reminders need a person who was on the firm's records before the call, not a new_person. If Zero refuses the task, it adds no one. If only one person on the firm's records has the email, Zero gives the task to that person and adds no one. With optional floor_plan, it starts a 3D plan for property instead of an email task and returns a link where the owner reviews and publishes it in cf0. When Zero setup is incomplete, the result is needs_setup, and set_up_agent finishes the setup steps.

give_agent_task

Stages the homes that an owner already advertises as drafts for review on cf0. text holds the owner's own ad text of one or more homes, and market holds their cf0 market code. cf0 reads the homes, the rent text and the deposit text from it, and keeps rent and deposit as written. cf0 does not open links, and it refuses text that is only links. photo_links holds links to the owner's original photo files of the one home in text. It refuses photo links from listing portals. connection names the software that holds the homes, and the result links to the cf0 page that connects it. The result gives the link to the review page, the number of homes, and the missing fields and the draft link of each home. It never lists or publishes a home. The owner checks each home on cf0. The same text again updates the same drafts and adds no second draft. For one home from the owner's own answers, save_home is the tool.

import_listings

Changes the viewing or the record of one renter on the user's homes. The ids come from the renters of ask_agent. confirm_viewing confirms a viewing, and cf0 emails the renter the invite with the visit link. cancel_viewing cancels a viewing, and an optional message goes to the renter by email in the same call. message_renter emails the renter of a viewing or of an enquiry from cf0 with the text of message. move_stage moves an enquiry to another stage: enquiry, prescreened, tour_booked, toured, applied, lease_signed or fee_invoiced. add_note adds a note to the renter's record. Each action takes two calls. The first call changes nothing. It returns needs_confirmation with a preview and a confirm_code. The second call has the same arguments and the confirm_code, and does the action. The user agrees to the preview between the two calls. A viewing cannot move to a new time. The result gives a status, a message and a link to cf0. Contact details are not in the result.

manage_renter

Adds a home draft, or replaces fields of a staged draft. It never publishes a home. rent_owner_text and deposit_owner_text hold the owner's own words. The server does not change, round or calculate these amounts. The draft takes the city, address, layout, private label, availability date, term and time zone. The result lists missing draft fields and readiness steps. It returns unread_money when it cannot read an amount. It refuses a deposit above the market cap. When the firm has not accepted the lettings terms for the market, the result is confirm_terms with the terms summary, the terms link and an accept_terms_code. accept_terms_code in a later call records the acceptance and names the user as the approver. With unit_id, it changes a home on cf0, listed or not: the rent and deposit text, deposit_shown, available_from, furnished, bedrooms, bathrooms, layout_name, address_line, building_name, min_term_months, private_label, timezone and added facts. remove_facts removes facts by text or id. confirm_available true confirms that a listed home is still available. A home that a firm approver listed changes only through that approver. A layout that other homes use keeps its bedrooms, bathrooms and name. The address and building name of a building with an ownership proof, or with a listed home, do not change. The result lists no firm setup steps. With layout_id, it adds facts to a layout.

save_home