MIZAN API

Every home. One API.

Give your systems and AI agents the home's record and prepared cases, only with the household's permission.

Roadmap
HomeGraph · hm_12cedarThe home's current record for your systems and AI. Each request is limited to what the household allows.
Illustrative · Roadmap
homegraph "hm_12cedar"12 Cedar Road, Bristol
facts[14]7 verified · 6 estimated · 1 not granted
relationships[5]mortgage → lender · policy → insurer
cost_lines[7]£2,840 / month
events[6]fixed_rate_end · 4 Apr 2027
permissions[4]2 granted · 1 awaiting · 1 not granted
evidence[3]statement · schedule · certificate
prepared_work[3]renewal · boiler · retention
decisions[ ]owned by institutions
verified_outcomes[2]boiler service · policy
readshomescore (five rings) · total_cost_to_own
historyrecorded · corrections added, never overwritten
Event flow · one fixed-rate end · months before 4 Apr 2027
9 months ahead
fixed_rate_end.detectedfrom a verified mortgage fact
6 months ahead
prepared_work.createdretention case · sourced facts
6 months ahead
permission.requestedwhat · with whom · why · until
6 months ahead
destination.approvedchosen by the household
5 months ahead
prepared_work.deliveredto an external institution or its agent
Primitives

The building blocks of HomeGraph.

Homes, facts, relationships, events, permissions, evidence, prepared work and verified outcomes. Connectors, APIs and MCP are how your systems and agents reach them. Shown as a concept; names will change with early-access partners.

homeseventspermissionsprepared_workconnectorsmcpRoadmap
// read a home from HomeGraph: facts arrive with source and permission
const home = await mizan.homes.retrieve("hm_12cedar");
home.facts.find(f => f.key === "rebuild_value");
// → { value: 265000, state: "verified", source: "policy_upload",
//     as_of: "2026-10-02", permission: "perm_ins_docs", evidence: "ev_schedule" }
home.relationships;  // → mortgage → lender, policy → insurer (as permitted)
Governed by default

Some calls are meant to fail.

An agent can only see what the household has permitted, for the purpose it was permitted. A refused call explains itself, so your agent can ask instead.

home.read · bank_transactionsREFUSED
await mizan.homes.read("hm_12cedar", { scope: "bank_transactions" });
// → 403 permission_not_granted
// { scope: "bank_transactions", state: "not_granted",
//   alternative: "cost_lines.estimated",
//   next: "permission.request with a purpose" }
Declined is an answerNot granted, or declined, is a valid state. The agent works from estimates and can ask again only with a stated purpose.
Every call states who is asking and whyEvery call names the agent, the institution and the purpose. MIZAN checks the permission for that request.
Decisions are not callableThere is no endpoint to approve a loan, price a policy or give advice.
Everything is written downEvery read, request and handover is recorded. Entries are never altered; corrections are added, and deletion follows the household’s rights.
Ways in

Where your code meets the home.

We are building these with early-access partners. Status is shown on each.

HomeGraph APIRead homes, facts, reads and events.Roadmap
EventsWebhooks when something changes in a home.Roadmap
MCP serverTools for agents, checked against permissions.Roadmap
ComponentsThe home experience inside your app.Coming soon

Better information on every home you insure or lend against.

MIZAN PREPARES · HOUSEHOLDS PERMIT · INSTITUTIONS DECIDE

tahir@mizan-os.ai