Docs / Getting started

Start here

You have a tenant of your own on a9script. This page is what you received, what to do in the first hour, and where the platform will stop you — so the first refusal you meet is one you have read about.

What you received

• The authoring address: https://a9script.lengauer.biz. Sign in there; everything you build lives there.
• Your endpoints’ address: https://hooks.a9script.lengauer.biz. A webhook you configure is reached under this host, and so is an API or MCP endpoint you expose.
• An invitation mail. Its link works once, for 48 hours. If it has expired, ask the operator for a new one; nobody can hand you a password.
• A tenant with two environments, sandbox and production. They are sealed off from each other; the only way from one to the other is a promotion you perform.
• Your role: tenant admin of your tenant. You invite colleagues, open write probes for the sandbox, allow egress ranges, and clear health marks.
• Session limits. A browser session ends after 30 minutes idle or 12 hours absolute; the login screen says which limit signed you out.

First sign-in

Your invitation link sets a password, and the platform then asks for a second factor: an authenticator, and recovery codes shown once, each good for one use. Nothing is switched on until a code from the authenticator proves it holds the secret, so a mis-scanned code locks nobody out — and if both the authenticator and the codes are lost, an administrator clears the factor and you enrol again with the password alone. People and access is the page that walks all of it.

Three things worth the first hour

• The sandbox. The environment switch is in the title bar, and sandbox is where Test, debug runs and probes are allowed.
• What this platform is — what is configuration and what is code, which is the one idea everything else rests on.
• Your first automation, in the browser, and then the endpoint it made called with curl from Calling your own endpoints.

Then from a terminal

Mint a token in the browser under your account. A token names one environment when it is minted — there is no default — and expires within 14 days. Leave the credential facet off unless the token has to change connections; a script references a connection by name and never needs it.

Then, in order:

a9script login https://a9script.lengauer.biz
a9script whoami
a9script entity list
a9script describe jira
a9script probe JiraGetIssue --input '{ "key": "KAN-9" }'
a9script apply ./my-integration --dry-run
a9script apply ./my-integration
a9script run on-issue --debug
a9script history
a9script inspect <run> <seq>

Every command answers JSON under --json; exit codes are 0 ok, 1 error, 2 validation. A stepped run (run --step, then position, continue, abort) parks after every external call. lock status and lock release say who holds the environment’s edit lock and give it back. The whole reference is Command reference.

Then with an assistant

The authoring surface speaks MCP at https://a9script.lengauer.biz/api/mcp, with the header Authorization: Bearer <your token>. Hand the assistant the authoring skill: the loop is the tools. Over this surface run answers at once — read history for the outcome. The assistant will ask you, by name, for four things it cannot do: a credential, a write probe in an environment where the switch is off, anything in production, and a decision about a write nobody asked for.

Limits you meet first

The complete table is Limits and safety.

What to watch out for

• Set a mail account to record while building; a redirect sends every recipient’s mail to one inbox; only deliver reaches the real addresses.
• Outbound calls to private addresses are denied unless a tenant admin allows the ranges, so a system inside your own network is not reachable from the beta.
• A credential never travels to production: promote, then enter it there.
• --debug, --step and probe are sandbox-only; production refuses them before anything runs.
• Write probes are off for tokens until a tenant admin switches them on for the sandbox.
• apply never deletes; remove an entity in the browser.
• A top-level return is the run’s result; without one, the final value of a top-level output variable is.
• A health mark stays red or amber until somebody acknowledges it.
• A model’s answer is input; validate it like any other.

Who to write to

office@lengauer.biz — say which tenant, which environment and, for a run, its id. We answer within two working days.