a9script

Get started

From invitation to first run

You ask for a tenant by mail. A person creates it and invites you by mail. From there, everything below is yours to do.

What arrives

  • An invitation mail whose link works once, for 48 hours.
  • A tenant with a sandbox and a production environment, sealed off from each other.
  • Your role: tenant admin — you invite colleagues, open write probes for the sandbox, allow egress ranges, clear health marks.
  • The authoring interface at https://a9script.lengauer.biz; your endpoints under https://hooks.a9script.lengauer.biz.

The first hour

  1. Set a password at the link and enrol an authenticator; save the recovery codes you are shown once.
  2. Open the sandbox and read what this platform is.
  3. Walk your first automation: a webhook arrives, a script runs, a call goes out.

From a terminal, or with an assistant

Mint a token bound to one environment — it expires within 14days — and use the command line, or hand an assistant the authoring skill and the MCP address. Both take the same loop: look, probe, write, lint, apply, run with a trace, read, fix.

Start here, in full →

Where it stops you

  • Debug, step and probe are sandbox-only.
  • Private addresses are denied unless allowed; the beta's network is not yours.
  • A credential never travels to production.
  • A health mark stays until acknowledged.
What the beta gives you, and what it does not →

Ask for a tenant

The offer, how to ask and the terms are on one page.

Join the beta