Skip to content
CCOMMERCE OS
ProductHow it worksIntegrationsPricingSecurityDocs
Sign inStart free
Menu
ProductHow it worksIntegrationsPricingSecurityDocsSign inBook a demo
Commerce OS docs
Documentation homeGetting startedConnect integrationsBuild workflowsApprovals and logsTroubleshooting
Open workspace
Guide · 10 minutes

Set up the first working Ekvaar workspace.

The safest path is organisation first, verified intelligence second, connected tools third, and autonomy last.

Before you begin

You need an Commerce OS account, an organisation you are allowed to configure, and at least one supported model provider key. Add other service accounts only when a workflow requires them.

No shared base key
A new organisation should not receive AI access from another workspace. If a model works before your organisation has configured a key, treat it as a configuration fault and inspect the provider trace.

Create and verify the workspace

01

Create the organisation

Sign up, choose the organisation name and complete onboarding. The selected organisation becomes the boundary for settings, credentials, memory and work.
02

Add a model provider

Open Settings, choose Add new key, select the provider and paste the organisation-owned API key. Save it, then use the connection test.
03

Select verified models

Only models returned by a successful provider connection should appear in routing dropdowns. Assign a fast model for interactive work and a stronger model for complex reasoning only if needed.
04

Connect one app

Open Integrations and connect the smallest service needed for the first task. Prefer OAuth when the provider supports it.
05

Run a low-risk request

Ask Krishna for a read-only output such as a brief or report. Confirm the task shows its owner, timeline, model route and resulting artifact.
06

Enable a controlled action

Create or assign a workflow, require approval, then run it. Confirm no external change occurs until approval and that the provider receipt appears after execution.

Ready-state checklist

✓ Organisation is correct
✓ Provider test is live
✓ Only connected models appear
✓ Required app is connected
✓ Approval policy is defined
✓ Logs show the full trace
COMMERCE OS

A desktop for commerce teams. Orders, inventory, finance, campaigns and an AI workforce share one organisation.

ExploreProductHow it worksIntegrationsPricingSecurityDocs
AccountStart freeSign inBook a demoPrivacyTermsABATA
© 2026 ABATA · Commerce OS