SID

Getting Started

Welcome to the SID Platform. From first compile to production code in minutes.

Try it first — no account needed

You can run the real DIS compiler immediately, no signup, no card, no install:

  1. Go to sidai.live/try.
  2. Paste (or edit) an ADL spec. The default example shows a multi-entity clinic app with contracts, guards, and relations.
  3. Click Compile it. The compiler runs against the production gateway and returns a full codebase — backend, frontend, database, tests, Docker.
  4. Inspect the generated files in the output panel. The ADL is the source of truth; the code is a disposable build artifact.

Rate-limited: 5 compiles/hour per IP. For more, grab a free trial key below.

Full workflow (API key)

For more compiles, MCP integration, and workspace features, connect with an API key:

1. Get your trial key

Sign in with Google or a wallet at sidai.live/login. The dashboard mints a trial key instantly: 1,000 calls/month, 100 req/min. No card, no invite code required.

2. Connect via MCP or curl

Easiest — OAuth (one click): add the custom connector URL https://api.sidislab.com/mcp in your client, approve in the browser, and you are connected. No key to copy.

API key (scripts/curl): get a key from the API Portal and send it as Authorization: Bearer YOUR_API_KEY.

See MCP Setup for client-specific instructions (Claude Code, Cursor, Claude Desktop, scripts).

3. Build

Once connected, you build entirely through the SID MCP tools in your client — there is nothing to install or clone.

  • Pull the ADL reference: get_dis_docs(audience="adl_quickref") for syntax, or read the ADL Manual online.
  • Write your ADL specification — entities, operations, services, and topology in the ADL v2.0 language.
  • Validate: validate_adl checks syntax, semantics, and constitutional rules before any compilation.
  • Compile: compile_adl runs your ADL through the DIS compiler.
  • Poll with task_get, then pull the result with task_result and browse the generated workspace with get_workspace / download_artifact.
  • Prove provenance: verify_repo mints a signed asset passport (sealed SHA-256 → Merkle root → HMAC attestation); buyers check it with get_passport / verify_passport. Source stays sealed — only fingerprints, structure, and build/test outcomes leave the sandbox.

The internal mission tools (create_requirement / execute_mission) are not on the external surface — external callers build directly with ADL + compile_adl.