Create an account

You need an account to go beyond the built-in example pack: it is where your Developer license, your packs and your SDK downloads come from. The Community tier needs no account at all, so you can try the quickstart first and sign up when you want custom rules.

What an account gives you#

Sign up#

For the Helixor Code CLI, create your account with helixor signup or on the web at code.helixor.dev/signup Available. See Get started with the Helixor Code CLI. For a Developer license for the Decision Runtime, there are two ways in. Each is marked with its status today:

1. Send your request Available by email; Planned on the web

   Give your name, a work email, your organization, and a sentence on what you want to decide. The web form asks for the same four. When it is connected, you will also review and accept the Helixor license agreement there before your account is created.

2. Accept the license agreement Planned

   Sign-up shows the Helixor Software License Agreement. You cannot create an account without accepting it. See Accept the license agreement for the web and CLI steps.

3. Wait for review Available

   A person at Helixor reviews each request. There is no verification email in this flow; the review is the check.

4. Receive your license and the runtime Available on request

   Once approved, Helixor sends your Developer license file (<your-license-id>.hxlic) and the runtime wheels, with a SHA256SUMS file that lists their checksums. Licenses are issued by Helixor; the CLI cannot mint or sign one. The demo repository is public, so there is no repository access to grant. Put the license where the runtime looks for it:

   mkdir -p ~/.helixor
   mv ~/Downloads/<your-license-id>.hxlic ~/.helixor/helixor.hxlic
   chmod 600 ~/.helixor/helixor.hxlic
   

   Downloading the license and SDK from your account yourself is Planned. See SDK downloads for what the wheel includes and how to verify it, then follow Installation.

5. Check it works Available

   helixor-pack inspect-license
   

   ==============================================================================
    HELIXOR LICENSE FILE INSPECTION REPORT
   ==============================================================================
    License ID:       hx_lic_...
    Organization:     Your Organization (ID: org_...)
    Edition / Tier:   DEVELOPER (...)
    Status:           ACTIVE (364 days remaining)
    Signature:        Verified Authentic (Ed25519 Authority Key)
    ...
   

   With no license in place it exits 1 with LICENSE_NOT_FOUND and lists the locations it checked; see where the runtime looks.

Accept the license agreement#

Every account and every license is tied to a recorded acceptance of the Helixor Software License Agreement. The record names the exact version you accepted:

Accepting with helixor signup and helixor license accept is Available. The web form step below is Planned.

On the web#

1. Read the agreement Planned

   The sign-up form shows the agreement text with its identifier and a link to the canonical copy.

2. Tick the checkbox Planned

   The checkbox "I agree to the Helixor Software License Agreement" starts unchecked. The submit button stays disabled until you check it.

3. Submit Planned

   The form sends the agreement ID and digest you were shown with your registration. The server records your acceptance with the time it was accepted.

With the CLI#

helixor signup Available (in the helixor package from 0.4.35) prints a summary of the agreement, its ID, its URL and its SHA-256 digest, then asks you to type the acceptance phrase exactly:

I ACCEPT THE HELIXOR SOFTWARE LICENSE AGREEMENT

Anything else cancels sign-up, and nothing is sent. Instead of typing the phrase, you can pass the digest of the version you reviewed. It must match the current agreement digest, or the command stops without sending anything. Sign-up still needs an interactive terminal, for the six-digit code it emails you:

helixor signup --accept-license-agreement ab2e1e2a67e5b99165cc6f4f8c9713e2e8e525dba893797f4f94cbe50a399807

helixor license accept uses the same agreement, the same phrase and the same --accept-license-agreement <sha256> option. See the CLI reference.

What the server enforces#

• No acceptance, no account. A registration without the agreement fields is rejected with HTTP 422 and LICENSE_AGREEMENT_NOT_ACCEPTED. Planned
• Only the current version. An agreement_id or agreement_sha256 that does not match the current agreement is rejected with HTTP 422 and LICENSE_AGREEMENT_MISMATCH. Fetch the current version and review it again. Planned
• No acceptance, no license. A license is issued only for an account with a recorded acceptance of the current agreement version. Planned
• A new version needs a new acceptance. When Helixor publishes a new agreement version, you accept it before a license is issued or renewed. Planned

The accepted version is also written into your signed license. See License file.

Public registration endpoint#

Scripted onboarding uses two endpoints on the Helixor licensing service Planned. First fetch the current agreement:

GET /api/v1/legal/license-agreement

{
  "agreement_id": "helixor-software-license-agreement-v2",
  "title": "Helixor Software License Agreement",
  "url": "https://helixor.dev/legal/license-agreement.html",
  "sha256": "ab2e1e2a67e5b99165cc6f4f8c9713e2e8e525dba893797f4f94cbe50a399807",
  "text": "# Helixor Software License Agreement\n..."
}

Then submit the registration request with the agreement_id and agreement_sha256 you accepted. Both are required:

POST /api/v1/registrations/request
Content-Type: application/json

{
  "company_name": "Example Corp",
  "contact_name": "Ada Example",
  "contact_email": "ada@example.com",
  "problem_statement": "Guard what our support assistant may send.",
  "agreement_id": "helixor-software-license-agreement-v2",
  "agreement_sha256": "ab2e1e2a67e5b99165cc6f4f8c9713e2e8e525dba893797f4f94cbe50a399807"
}

A request with a missing or mismatched agreement is rejected with HTTP 422 (LICENSE_AGREEMENT_NOT_ACCEPTED or LICENSE_AGREEMENT_MISMATCH); see Errors. An accepted request goes into the same review queue as an emailed request.

Request access#

Until self-serve sign-up reaches you, request a Developer license from the Helixor team. Include your organization, your name, a work email, and a sentence on what you want to decide. The request goes into a review queue; once it is approved, Helixor sends you:

• your Developer license file (.hxlic),
• the runtime wheel for your platform, with its SHA-256 checksum,

The helixor-decision-demos repository, whose examples the Quickstart runs, is public: clone it without a request.

Email hello@helixor.ai with the subject "Developer license request". A license is issued only once you have accepted the current Helixor Software License Agreement. A public registration endpoint for scripted onboarding is Planned; see Public registration endpoint.

Keep your account secure#

• Your license is a secret. It holds the key that decrypts your packs. Never commit it, paste it into a ticket or put it in a URL. See Licensing and tiers.
• One license per environment where you can, so a leak in one does not expose the others.
• Tell Helixor immediately if a license file is exposed. Revoking and reissuing licenses from your account is Planned; today the team reissues on request.

Next#