AI agents & governance
Beyond chat and reports, the console defines governed multi-step agents for your brand — with a builder and governance view. Publishing an agent does not authorize a paid execution.
Agent Hublink
- check_circleExpansion Agent (/franchisor/agent-hub) — a five-step market-entry workflow: market analysis, territory scoring, opening sequence, financial model, and a go/no-go blueprint for a target country and regions. Any execution, where offered, requires a separate franchisor action and displayed Koin/Sikka price confirmation.
- check_circleRecruitment Agent — designed to build an ideal-operator profile for your brand and score a candidate list you provide. Any execution, where offered, requires the same separate action and displayed-price confirmation.
- check_circleMy Agents — the custom agents you publish. Publication alone never authorizes a paid run; any execution control must show the Koin/Sikka price and obtain confirmation first.
- check_circleRun History — your past expansion and recruitment runs with status, brand, timestamps, and Koin cost.
Build your own agentslink
The agent builder (/franchisor/agent-builder) defines custom research agents grounded in your brand context — name them, define what they research, test them in the builder, and publish. Publishing stores the configuration; it does not authorize execution.
Published agents do not start because a lead arrives or because your wallet has funds. Where execution is offered, it must remain behind a separate franchisor action and confirmation of the displayed Koin/Sikka price.
Governancelink
The governance dashboard (/franchisor/governance) is your oversight surface for AI activity on your account: agent inventory and status, run outcomes, and audit trails. Use it to review what your agents did and retire what you no longer need.
The franchisor AI chat lives at /klick/franchisor-chat and is grounded in your brand, organization, and candidate profile — see Contextual identity for how that grounding is assembled.
AI Models & Providers (/franchisor/settings/ai) lets an approved franchisor choose automatic routing or an individual model where user choice has been enabled for that account, page, capability, or output. Only deployments that pass health, policy, commercial, and billing gates can be selected. Azure is the initial activation rail; Gemini remains visibly marked Coming Soon until its rail passes the same checks.
Any paid use records Kariant’s final retail charge—not the model provider’s raw list cost—in the unified KashFlow ledger. The charge is shown as Koins globally and Sikka in India. Changing a preference never authorizes an automatic lead-scoring or agent run; the franchisor must still start and, where required, confirm each paid action.