CLERK · TEST MODE

Sign-in routes to a sandbox. Google OAuth and Paddle checkout are unreachable until you swap to pk_live_ keys in Vercel.

Setup guide →

Documentation

Build on the same execution system the product runs on.

Everything needed to integrate Alabobai into production workflows, from first quickstart to API, SDK, CLI, and operator-grade automation.

Private early access for founders, operators, and executive teams.

alabobai.ai/docs
Alabobai
Alabobai
AlabobaiDeep Research
Export
Share
Sources Found — 23
Google Scholar8 papers
arXiv11 papers
Semantic Scholar4 papers
Synthesizing report...88%

First outcome in under 10 minutes

Open quickstart
  1. Sign in and create one workspace goal (30 seconds)
  2. Run a single execution prompt from the template library (3 minutes)
  3. Review execution receipt + citations and export the output (4 minutes)
  4. Share result with your team and queue follow-up automation (2 minutes)

Tip: use one narrow business objective first, then scale to multi-agent workflows after receipt review.

The docs should feel like the product: clear, governed, and ready to ship.

Quickstart, API reference, SDKs, and CLI all live in the same execution-first system instead of looking like a separate site.

Quickstart

Go from first login to first shipped outcome in under 10 minutes with guided execution templates.

API Reference

Core endpoints cover chat, execution, memory, and subscription workflows. Use token-scoped access with least-privilege defaults.

SDKs

JavaScript/TypeScript integration helpers for product teams shipping quickly with strong type safety.

CLI Tools

Run local-first automations from terminal with deterministic command logs and reproducible workflows.

CLI execution

$ alabobai execute "launch revenue workflow"
✓ Context bridge loaded
✓ Agent squad assembled
✓ Evidence-linked execution report generated