01 · Name
A corporate identifier that outlives providers
Your CorpID and Corporate Digital Name remain stable while keys, tenants, devices, people and AI vendors change underneath them.
Corporate authority for the agent era
Give your corporation a digital name every identity system can carry.
Connect your legal company to Microsoft, Google, AWS, your people, machines and AI agents — so customers, investors and employees can verify who is actually authorized to speak and act for you.
Live reference specimen
Rootz Corp.
Corporate Digital Name
Rootz Corp.
0xD36AAf65a91bB7dc69942cF6B6d1dBa4Ef171664
Legal corporation→
Corporate Digital Name→
Governance→
Enterprise identities→
Signed actions
Legal entity
Referenced
Digital name
Asserted
Authority policy
Gap
The missing layer
Credentials are not corporate authority.
Microsoft can prove a credential came from your tenant. Google can prove a workload belongs to your organization. CorpID gives those credentials a durable corporate principal and a discoverable authority chain.
02 · Authority
Governance before delegation
Publish how the corporation authorizes digital identities, provider bindings, agents, consequential actions, rotation and revocation.
03 · Evidence
Every edge says what proves it
Assertions, observed facts, provider-issued credentials and signed messages remain distinct. “Signed” never silently becomes “true.”
Compose, don't replace
A thin fabric across systems you already use.
CorpID is not a new directory, CA, SSO product or wallet stack. It defines the corporate root and the evidence relationships that existing identity systems can carry.
Legal corporation
ACME Corporationstate / national registry evidence
Referenced
Corporate Digital Name
corp:acme:0x8A…41F2durable cryptographic name
Active
Governance policy
Corporate Digital Authority Policy v3who can bind providers, delegate agents and revoke authority
Signed
Microsoft Entra
Enterprise credential carries CorpID claimprovider evidence ↔ corporate identifier
Bound
AI evaluation agent
gpt-eval-prodscope: test Rootz endpoints · expires in 60 minutes
Delegated
Signed message
“Run regression R1–R9 against production”exact bytes + signer + policy + expiry + result can travel together
Verifiable
Message-based authority
No login is the root of authority.
A session may help a human use the control panel, but the durable evidence is the signed authorization message itself: who issued it, what it allows, for whom, until when, and what corporate policy made that delegation valid.
Signed intent
Authorize the exact action
“This AI may test these endpoints for the next hour” becomes a portable evidence object rather than a checkbox buried inside an application database.
corporation: corp:rootz:0xD36A…1664\naction: run-regression-suite\nsubject: gpt-eval-prod\nscope: [origin, politics, cars]\nexpires_at: 2026-09-07T20:00:00Z\nnonce: …\nsignature: …
Epistery native
Bind an IdentityContract without giving CorpID control
CorpID prepares one message. An existing Epistery rivet executes it against the contract's public profile. The contract publishes the CorpID reference itself; CorpID publishes the contract back. No privileged Rootz key is inserted.
Bidirectional: CorpID → Epistery IdentityContract, and _profile.corporate_authority → CorpID.
Built for relying parties
Verification should answer a question, not flash a green badge.
The verifier tells a customer, investor, employee or another AI what the corporation is, what issued a credential, what policy connected it to the corporation, whether the actor had the right scope at that time, and what evidence supports every link.
Customer
“Was this agent allowed to sign this order?”
Follow the delegation, provider binding and authority policy that existed when the message was signed.
Employee
“What authority does my credential actually carry?”
Separate corporate authority from mere possession of a Microsoft, Google or device credential.
Investor
“How does this company govern machine authority?”
Read the corporation's published process, policy history, rotations, revocations and material gaps.
Start with the actual primitive
Your company already has identity systems. Give them a corporate root.
Create the corporation record, establish the Corporate Digital Name, publish governance, then bind the systems and agents you already use.