ENTITY developer reference
Register interest in ENTITY
Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.
Register interest in ENTITY
Use the existing ENTITY enquiry form to express interest in early access. This does not create a customer account, workspace, API credential, paid plan or service entitlement. There is no promised activation date.
ENTITY is preselected on the form. Provide your name, email, organisation and the requested workflow details so the team can review your interest and respond. No password or payment is needed. This is an enquiry, not confirmation of a place or an activation date. You can withdraw your interest by contacting privacy@sustema.io.
Pending account registration and sign-in
Customer account registration and sign-in are not enabled through this page until the account connection is available. Documentation and synthetic examples remain open without an account.
When the account connection is available, the sign-in link below opens the ENTITY account page. You can then create a pending account or sign in to an existing one. Review the account terms and privacy notice shown there before registering. A pending account records your interest; it does not provide a workspace, API credentials, free testing or paid service access.
Before creating an account
Before registering, complete the supported email-verification and sign-in security steps. Email verification alone is not multi-factor authentication. Pending registration is free and does not require a payment card or company registration.
Review the account terms and account privacy notice supplied by the account page and make an affirmative choice before continuing. Do not enter an email address, password, recovery code or other credential into an example. Documentation and synthetic examples remain open without an account.
Verify access before continuing
A return from a hosted sign-in page alone does not establish a session. The application must confirm the current session with the server before showing private workspace information. Interrupted or cancelled verification must not be presented as successful sign-in.
Account terms and free-testing acceptance are separate. Opening a workspace does not itself provide funding, free-tier consent or company membership. Use the exact versioned terms and service-specific privacy information supplied by the accepted access flow; website privacy information does not replace account-service information.
When service access becomes available
A pending account does not provide a workspace, credentials or usable allowance. The following workspace guidance applies only after service access is separately made available.
Choose the right workspace
A personal workspace and a company workspace are separate. Joining a company requires a valid invitation or the defined company-formation and authority checks. Sharing an email domain does not establish membership. Personal request history and credentials do not silently transfer into a company workspace.
Check the selected workspace, available capabilities, readiness and usable allowance before work. A pending allowance is not a reason to repeat activation. Free testing is not an unlimited service or production entitlement.
If you cannot sign in
Use another supported passkey or a recovery code through the qualified secure sign-in flow when available. Resetting a password does not remove the second factor. Recovery must not replace a second factor with an email alone.
If every factor is lost or something looks wrong, the exceptional recovery flow needs its own qualified intake and human checks. Its acknowledgement does not sign you in, change a security setting or promise instant restoration. That private recovery flow is unavailable here; the general contact page is not a substitute for identity verification. Never send passwords, tokens, client secrets or recovery codes in a general enquiry.
After restoring access, confirm the current workspace and authority. Nothing should automatically rerun merely because a session was restored. Preserve any uncertain original operation and follow the recovery guide.
Next: prepare application credentials or read the synthetic first request.
Account documents
Read the ENTITY account terms and account privacy notice for pending registration. When customer account registration becomes available, that flow will supply the applicable versions before acceptance. The enquiry uses the website privacy notice and does not accept customer account terms.