Can AI agents automate Husbanken Kobo?

The best evidenced path into Husbanken Kobo is the documented Kobo Bolig API, not the staff or citizen screens. Husbanken publishes Kobo Bolig API v1 as OpenAPI 3.0.3 REST at api.husbanken.no/kobo/boligapi/v1, with a Kobolab host at api.demo.husbanken.no. The specification covers listing, creating and updating municipal housing, owners, allocations, reservations, tenancies, photos, contact units and the FDVU webhook registration. Calls require a Maskinporten token for the private scope husbanken:kobo/boligapi.write after Husbanken assigns that scope to the municipality and its supplier, the municipality delegates the API in Altinn, and Husbanken opens the supplier IP or webhook domain. That assignment gate is the material limit. Coverage is housing and tenancy for FDVU systems; the specification is not a public case-management API for the fagsystem or citizen self-service. Husbanken also documents a webhook the FDVU host must expose, and one-off CSV boligimport in the fagsystem. Kobo is Husbanken's free digital service for municipal housing: a municipal fagsystem and citizen self-service. Husbanken states Kobo does not replace FDVU systems such as LAFT, Facilit, Famac, Plania or MainManager, including their rental modules. The product page says archive delivery uses the Fiks platform; Husbanken's archive notes specify KS SvarUt journal posts and say that path is not KS Fiks Arkiv. Vendor copy dated 21 May 2026 lists 149 signed data-processor agreements. This record is not KoboToolbox, Visma Flyt Sosial, Tietoevry Socio or LAFT.io. First-party MCP ownership is not established. Computer-use viability is unassessed.

Best path today: api · Overall automatability: 5/10