Organization
The agent belongs to an organization whose configured domain control was verified for the current deployment profile.
AI agent identity
Totem links a registered agent to the organization it represents, then carries that identity into recipient-bound credentials and request-bound proof. The receiver checks the identity against current authority before acting.
A useful machine identity tells the receiver which organization controls the agent and which key authenticated the workload. It also needs lifecycle state. If the organization, agent, key, relationship, or credential is no longer valid, an old signed artifact should not keep working.
Totem registers agents inside an organization that has proved control of its configured domain. Presenting and receiving workloads use separate scoped keys. The platform stores the public verification material and checks the active organization context on the server.
The agent belongs to an organization whose configured domain control was verified for the current deployment profile.
The credential and presentation name one registered, active agent rather than a shared human account or an unlabeled process.
Authority is issued for a named receiving organization. Proof for one counterparty does not become general access elsewhere.
Agent, key, credential, and company-relationship revocation take effect in live verification checks.
Knowing the agent’s organization does not prove that the request is safe, accurate, or contractually valid. Totem adds the action, recipient, time window, request digest, and current policy state to the decision. The receiving service still decides whether to perform the business operation.
This separation matters in cross-company automation. The presenting agent cannot define the receiver’s policy, and a passing identity check cannot authorize a different action. Read the AI agent authorization page for the request-level controls.
TotemLayer
See how Totem binds identity and current authority to one exact cross-company request.