Self-serve EU starter

Run a first EU AI Act starter check on your own agent

Use this page to see all self-serve starter commands in one place. Pick the block that matches the package you want to work on now.

Commands to run

Use the full package block for the broader high-risk path, add Article 50 when transparency is also in scope, or use the standalone Article 50 block when transparency is your only EU scope.

See pricing See sample package

Full EU package starter

Run the EU starter against your already-running adapter when you want the broader high-risk package path without Article 50 in scope.

Starter command

cd products/eu-ai-act
npm install
npm run starter -- --baseUrl http://localhost:8787 --systemType fraud --profile my-agent

Full EU package + Article 50 starter

Run the broader EU starter first, then run the Article 50 packaging commands when transparency is also in scope for the same system.

Starter command

cd products/eu-ai-act
npm install
npm run starter -- --baseUrl http://localhost:8787 --systemType fraud --profile my-agent

Article 50 package command

node scripts/article-50-package.mjs --reportDir <path> --outDir <path>

Article 50 verify command

node scripts/article-50-verify.mjs --reportDir <path>

Standalone Article 50 starter

Use this mode when transparency is your only EU scope and you want the focused Article 50 packaging and verification commands.

Article 50 package command

node scripts/article-50-package.mjs --reportDir <path> --outDir <path>

Article 50 verify command

node scripts/article-50-verify.mjs --reportDir <path>

Before you run it

Node.js 20 or newer is installed on the machine where you run the command.
For the full EU starter, your adapter is already running and responds to GET /health and POST /run-case.
For the Article 50 packaging commands, you already have a report directory with retained outputs or artifacts relevant to Article 50.

What you get

After this run you can see whether the toolkit can reach your agent and whether the selected self-serve path is strong enough before moving to the first real package.

A first self-serve signal before the first real package.
A lightweight broader starter result or focused Article 50 evidence, depending on the commands you run.
A cleaner go / no-go decision before paid help.

What this is not

Not the final role- and scope-selected package.
Not the final document set for your system.
Not a conformity assessment or external review result.

Need paid help?

If you want help reaching the first real package faster, go to pricing.
The paid path uses real cases and real runs for the selected package path.

FAQ

Frequently asked questions

What is the EU AI Act starter check?

The starter check is a self-serve first run on your own agent or retained report directory. It helps you see whether the workflow can produce a lightweight EU-shaped result before your team invests in a full package.

What do I need before running the starter?

For the full package starter, you need Node.js 20 or newer and a running adapter that responds to the expected health and run-case endpoints. For Article 50 packaging, you need a report directory with retained outputs or artifacts relevant to the transparency branches you want to test.

Is the starter the same as the full EU AI Act package?

No. The starter is a first signal and go/no-go check. The full package still needs the selected role and scope, written dossier sections, linked evidence, exports, and human review before it can become the review-ready package for your system.

When should a team move from starter to paid help?

Move to paid help when the starter shows the workflow is relevant but adapter setup, cases, comparable runs, or the first real package handoff are blocking progress.

Can the starter be used for standalone Article 50 work?

Yes. The starter page includes a standalone Article 50 mode for teams whose current EU scope is transparency evidence rather than the broader high-risk package.