Quickstart

Pre-beta: Cendriix has no GA customers yet. This guide reflects the design-partner preview — not every CLI command or workflow slug in older docs is shipped.

Get from access request to your first orchestrated run using the web app. CLI automation and npm install come after the CLI package publishes.

Step 1 — Request design-partner access

Apply as a design partner  or book a walkthrough . We provision workspaces manually during pre-beta — there is no self-serve signup yet.

curl -X POST https://api.cendriix.ai/v1/intake/access-request \
  -H "Content-Type: application/json" \
  -d '{"name":"…","email":"…","company":"…","message":"Design partner request"}'

Step 2 — Sign in to the app

Once provisioned, sign in at app.cendriix.ai  with Cognito (email invite). Cendra, the run composer, and approval gates live in the Director workspace.

Step 3 — Connect cloud (preview)

BYO-cloud uses your AWS account. In preview, connect via the app Settings → Cloud providers UI, which calls POST /v1/cloud-providers. CloudFormation one-click templates and CLI workspace cloud connect are on the roadmap.

No source code leaves your VPC. Agents execute in your cloud; the control plane stores metadata and audit pointers only.

Step 4 — Trigger a run

From the app, file a need in Cendra or start a run from the Runs panel. The API equivalent is POST /v1/runs with a workflow your workspace supports.

curl -X POST https://api.cendriix.ai/v1/runs \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{"workflow":"<your-workflow>","metadata":{"source":"quickstart"}}'

What’s next

• API reference — live Fastify routes
• CLI reference — target commands (package not on npm yet)
• Security  — subprocessors, retention, disclosure
• Design partners  — why join before GA