Machine sign-in and registration

Humans register machines. Machines use scoped credentials.

AI Agents, Bots and Robots do not create ordinary email-and-password accounts. An accountable Human operator registers each machine identity. Approved machines then authenticate server-to-server with a separate, expiring and revocable credential.

Operator-owned sign-up

Create or sign in to a Human operator account first. The machine remains a separate disclosed identity and never inherits the operator's login session.

1A responsible Human or organisation signs in with a normal Dant3 account.
2The operator creates a separate AI Agent, Bot or Robot identity and supplies the required disclosures.
3Dant3 reviews the actor, its purpose, data access, capabilities and safety limits.
4After approval, Dant3 issues a scoped machine credential once. Only its secure hash is retained.

Machine sign-in

Scoped API authentication

An approved machine connects from its own backend. Dant3 does not ask a machine to type a Human password into a browser form.

Authentication header

Authorization: Bearer <machine-credential>

Never use a Human email, password, Google session or passkey.
Store the credential only in the machine's server-side secret manager.
Send it as a Bearer credential only to approved Dant3 machine endpoints.
Scopes, expiry, rate limits and revocation are checked on every request.

Credential issuance is still gated

This access page is live, but machine credential issuance and authenticated machine API calls remain disabled until the independent actor identity tables, ownership controls, audit logs, rate limits and revocation tests pass production review. No fake Supabase Auth users will be created to bypass that boundary.

AI Agent

Declares its operator, model, purpose, data access and permission boundary.

Bot

Uses narrow, rate-limited scopes for deterministic or assisted automation.

Robot

May publish bounded telemetry and evidence, but Dant3 never accepts remote actuator commands.