Loading…
Loading…
FlozentAi lets an AI agent act inside software you already run, without handing that agent unscoped access. Connect your systems, decide what is callable, and keep a person between a proposal and a consequential action.
Import an OpenAPI document or a remote MCP endpoint. FlozentAi reads it and proposes the individual actions it found — nothing becomes callable until a person approves it.
Browse integrationsWorkspace, application, environment, host tenant, end user. Every run resolves to one of each, and the agent cannot widen its own scope because the scope comes from the token.
How the model worksConsequential actions pause and show the exact arguments. An approval authorises that proposal — change it and the decision goes back through the gate.
Security and governanceIdentity, retrieved context, policy decision, provider request, result. Runs stream while they execute and can be resumed if a connection drops.
Runs and approvalsAlmost every object in the console is a level of scope. Getting the levels right is the difference between a system that stays manageable at ten customers and one that does not.
| Level | What it represents | Who creates it |
|---|---|---|
| Workspace | Your company — the organization that bought FlozentAi | You, at sign-up |
| Application | One piece of software agents act inside | You, in the console |
| Environment | Development, staging or production of that application | You |
| Host tenant | One customer account inside your application | You, or your signup flow |
| End user | One person inside a tenant | Created automatically on first sign-in |
One tenant per customer organization, with their users as end users inside it. Creating a tenant per individual user is the most common modelling mistake and it becomes expensive to undo.
Upload or paste an OpenAPI document, point at an HTTPS URL, or reference a remote MCP endpoint. A discovery worker reads it and proposes candidate actions.
Set its namespace, name, description, required permissions and risk level. Approving creates an immutable draft version; rejecting records your reasoning against that revision.
Give the HTTPS origin and the account to act through. The credential stays in your vault — FlozentAi holds a reference to it, never the value.
A deployment is the versioned bundle an application actually runs. Promote it per environment, and stop new runs with a kill switch if you need to.
Plain definitions for the vocabulary here — tool calling, token exchange, prompt injection, row-level security and the rest.
Browse the termsWhat you actually have to build to do this safely, and the cases where doing it yourself is the right answer.
Read the comparisonWhat happens to credentials, how tenants stay isolated, and what it costs to find out.
Read the answersThe product demo walks one agent across CRM, billing and commerce, and stops at the approval gate.