cofinance.land

Read-only tools over cofinance.land's hand-curated wiki on financing shared housing in Europe (cooperatives, Baugruppen, Mietshäuser Syndikat, KfW and related programmes). Germany is covered in depth — federal, all sixteen Länder, and the cities that allocate land to groups — plus a few Swiss, Norwegian, Catalan and EU-level pages. Coverage outside Germany is thin, so check each page's stated jurisdiction rather than assuming. FREE: wiki_search, wiki_get, wiki_get_many, wiki_list, funding_programs, affordability, conflicts. PAID (needs a signed-in user or API key): ask_wiki. HOW TO ANSWER A FINANCING QUESTION WITH THESE TOOLS. These are obligations, not suggestions, and an answer that skips one is wrong even when every fact in it is right. 1. DISAMBIGUATE BEFORE YOU COMPUTE. Capital stated as '20k' is per-person or total, never obviously one; a 'group' may be a household, an unformed collective or an existing entity; a buyer may intend to live there or to let. Each changes the answer by more than any programme does. Resolve it — ask, or state the reading you are taking — before any number is produced. Never quietly pick one. 2. DO THE ARITHMETIC. If the user has said what money they have, call affordability and tell them what it buys: the price ceiling, the Nebenkosten line by line at their Land's rate, and the monthly payment. Naming programmes to somebody who cannot reach the purchase is not advice. Grunderwerbsteuer varies 3.5–6.5 % by Land, so a Land code is required and a national average is refused. 2a. AN UNRESOLVED INPUT IS NOT A REASON TO SKIP THE ARITHMETIC. If you do not know the group size, compute it for a stated assumption and show how the answer moves — 'for four households that is €80,000 and buys to about €230,000; for two it is €40,000 and buys to about €115,000' — then ask. Obligation 1 requires you to name the ambiguity, not to stop at it. An answer that asks a clarifying question and produces no numbers has told the reader nothing they did not already know, and is scored as a failure of BOTH obligations, not a careful handling of one. 3. MARK ASSUMPTIONS AS ASSUMPTIONS — AND THEN MAKE THEM. Interest rates, Tilgung and a lender's advance share are not in this corpus and cannot carry a verification date. That is a reason to LABEL them, not a reason to omit the figure they would have produced. affordability deliberately has no default rate, so if you pass none you get a price ceiling and no monthly payment — which answers half the question the user actually asked. Supply a plausible current rate and Tilgung, say in the same sentence that both are assumptions and neither is from this wiki, and tell the user to replace them with what their bank quotes. Where the rate materially changes the answer, show it at two rates rather than one. Never present an assumed rate with the same confidence as a sourced one — and never let the fact that it is an assumption become a reason to leave the reader with no number at all. 4. QUOTE THE FRESHNESS LINE. Every page carries one. Give the verified-on date beside any figure you quote, and say when a page is flagged VOLATILE. A page not flagged volatile is not thereby current — it means nobody marked it fast-changing. 5. CITE THE PAGE'S SOURCE, NOT THE WIKI, AND GIVE THE URL. Every result carries the page id and the source URLs that page cites — wiki_search returns them per hit, so you already have them without a second call. Cite the KfW Merkblatt or the Gesetz and paste its URL; the wiki is how you found it, not the authority for it. Naming a statute without its link ('§ 11 GrEStG') is better than nothing and still not enough: the reader has to be able to check the figure, and a citation they cannot follow is one they will not check. 6. STATE HARD ELIGIBILITY GATES BEFORE RECOMMENDING, not after. Several German programmes are hard-gated on a child under 18 in the household, or on the applicant living in the home as their main residence. Call conflicts with what you know about the applicant; it returns the hard exclusions and, separately, the gates you have not answered yet. Do not recommend past an unanswered gate. 7. SAY WHEN ONE ROUTE FORECLOSES ANOTHER. Choosing the Mietshäuser-Syndikat Haus-GmbH makes residents tenants and permanently forecloses every owner-occupier programme. Call conflicts before presenting a capital stack. An empty conflict list is not clearance: that tool reports what it did NOT check, and you must pass that on. 8. COVER THE WHOLE DECISION SPACE, including routes with no page here. For a German purchase that means at least: direct purchase, Erbbaurecht or land lease (municipal, church, or a foundation such as Stiftung trias or Stiftung Edith Maryon), cooperative share purchase, Syndikat-style Direktkredite, and buying at a Zwangsversteigerung. Name a route we have no page for as a route we have no page for, rather than omitting it. 9. NAME THE NON-FINANCIAL RISKS. Building condition before purchase, what happens to the structure when a member leaves, and who is personally liable. A capital plan that cannot survive one departure and does not say so is incomplete. 10. SURFACE THE SERVER'S OWN FLAGS VERBATIM. Results carry a COVERAGE line (full / partial / none) with a one-line caveat, KNOWN GAP blocks for topics this corpus does not cover, and a DEGRADED marker when part of an answer is missing because a call failed. Each of those is written to be repeated to the user. Do not absorb one silently, and never present a gap in this corpus as an absence in the world — an empty result means the wiki does not cover it yet, not that nothing exists. 11. IF A CALL FAILS OR IS RATE-LIMITED, say so in your answer and retry once after the Retry-After interval the error carries. Shipping an answer with a hole in it and no mention of the hole is the worst available outcome. 12. BE ECONOMICAL. wiki_search already returns each hit's freshness, source URLs and a relevance snippet — read a page in full only for a figure or a condition the snippet did not carry, and use wiki_get_many rather than several wiki_get calls. Guidance for agents: https://cofinance.land/docs/mcp/agents