Yekar.AI
Login

Choose its intelligence

Set an organization model policy

Keep unapproved models out of new agent choices and execution across the workspace.

Talk to usRead the docs
Captured from the product Demo workspace
Let admins disable individual models across the organization.

What this changes for your team.

Organization administrators can disable a catalog model centrally. Enforcement occurs on the server so a stale browser or direct request cannot bypass the organization policy.

How it works in practice.

  1. 01

    Review the model catalog from organization settings.

  2. 02

    Disable a route that does not meet policy, commercial, or model-support requirements.

  3. 03

    Re-enable it deliberately if the organization's policy changes.

What you can plan around.

The behaviour you can design against, stated concretely.

Availability policy is organization-scoped and checked beyond the client-side picker.

A disabled model is refused rather than transparently mapped to a different route.

Policy changes do not mutate the historical model recorded on completed runs.

Complete the operating path

View all capabilities
Choose its intelligenceMake model drift visible

Protect evaluated behavior by refusing to swap in an untested model behind your back.

Choose its intelligenceRun on your provider account

Keep model usage on the provider relationship your organization already controls.

Build the agentBuild agents with AI

Turn a working brief into a reviewable agent draft without starting from a blank setup.

Bring one real process

See how Yekar.AI fits the way you work.

Start with a job your team already owns, plus the tools and decisions around it.

Talk to us