Permission is explicit
An agent identity is scoped to an organization and to the actions it may take. Reading, drafting and executing are separate decisions.
Houzle is building a business system where AI agents work with structured records, explicit permissions and a clear path to human review.
The API foundation is available. The full product and self-service sign-up are still in development.
The agent may draft a reply. Sending requires separate permission or human approval.
Agents need useful access. Businesses need boundaries they can inspect and change.
An agent identity is scoped to an organization and to the actions it may take. Reading, drafting and executing are separate decisions.
Business records are structured. The design records where important information came from, when it changed and who is responsible.
Requests are designed around clear business intentions, idempotency and audit data so a person can understand the result.
A business action has a path: understand the context, prepare the proposal, apply policy and record the outcome.
Read a permitted account record and its next action.
Example of the intended flow. The full workflow is in development.
We are starting with the platform and CRM foundations, then adding the workflows agents need to do real business work.
Tenant isolation, identity, permissions, reliability and audit foundations are being built in the API.
Accounts, contacts, pipelines, opportunities, activities and conversations are the first business workflows.
Email connection, conversation context, drafts and human review are part of the initial product scope.
Quotes and orders come before purchasing and inventory. Full accounting and autonomous payments are outside the first release.
REST and OpenAPI are the base of Houzle’s agent interface. MCP support is being built over the same domain logic. The published reference shows today’s available routes.
Read the API referenceNot yet. Houzle is in active development. The public API reference shows what is available now; a self-service console and complete business workflows are still being built.
That is the goal. The architecture uses REST/OpenAPI as its base and is adding MCP tools, so business logic does not depend on one model or a private prompt. Business MCP tools are still in development.
The product design separates reading, preparing and executing. Policies can require human review for sensitive actions and the system records what happened. The end-to-end review experience is not released yet.
Complete accounting, payroll and autonomous financial transactions are outside the initial scope. The roadmap starts with CRM and then basic quotes and orders.
Follow what exists today in the public API reference. We’ll add the business workflows as they’re ready.
Explore the API