AUTONOMOUS AI AGENT
IDENTIFICATION
& CRYPTO SIGNING.
Verify, control, and authorize AI agents using cryptographic machine DIDs. Issue machine-readable verifiable credentials to non-human autonomous processes safely under Ed25519-signed enclaves.
BOT SPAM & MACHINE
IMPERSONATION.
In an era dominated by autonomous LLM agents and machine processes, traditional identity verification fails. Bots impersonate human users, steal server resources, and flood APIs without verified billing anchors or accountability.
Static API keys are highly vulnerable to leakage. If an AI agent's hardcoded secret key is leaked, malicious parties can hijack the system, leading to unexpected financial drain and automated data exfiltration.
Untraceable Automated Actions
Autonomous API requests lack secure cryptographic attestation back to a legally verified parent user.
API Abuse Vector
Malicious software agents spoof browser contexts, bypassing standard captcha and heuristic protection.
CRYPTOGRAPHICALLY BOUND
MACHINE IDENTITY.
UIID introduces `did:uiid:agent` standards. Every autonomous task agent is allocated a sub-identity bound directly to its human owner's physical passport KYC status, enabling real-world auditability with zero privacy exposure.
Agent Provisioning Tokens
Generate limited-scope asymmetric cryptographic key pairs specifically for autonomous processes.
On-the-Fly Attestation Signing
Agents sign API requests in milliseconds using Ed25519, ensuring cryptographic integrity for each operation.
MACHINE LEVEL TRUST
- ✓ Dynamic public/private key rotation
- ✓ Verified parent user KYC references
- ✓ Hardware-enclave execution proofs
- ✓ Non-custodial budget restrictions
AGENT IDENTITY SPECIFICATIONS
Self-Signing Keys
Agents utilize isolated private keys inside enclaves to perform programmatic authorization steps.
Parent Anchor
Cryptographic validation maps back to the master DID of the controlling organization.
Real-time Revocation
Instantly revoke any machine agent's active token from your central control dashboard.
Zero-Gas Minting
Agent identifiers are issued locally without any network transaction or consensus overhead.
AGENT DEPLOYMENT SEQUENCE
Token Issuance
The controller issues a machine-scoped provisioning token from their UIID developer dashboard.
Enclave Initialisation
The agent initializes its secure enclave, creating an independent, asymmetric cryptographic signing key.
Attested Request
The agent signs every outbound API payload. Servers verify the Ed25519 signature locally in microseconds.
AGENT SIGNING DEPLOYMENT
Integrate secure autonomous machine identity signing inside your Go services:
// Initialise secure machine client agent
agent, err := uiid.NewMachineAgent(&uiid.Config{
ProvisionToken: "uiid_prov_token_99182312",
HardwareEnclave: true,
})
if err != nil {
log.Fatalf("Enclave failure: %v", err)
}
// Generate attested request envelope
payload := []byte(`{"action": "execute_trading_strategy", "volume": 12.4}`)
signature, err := agent.SignAttestation(payload)
GLOBAL AGENT STANDARDS
did:key & did:peer
Fully compatible with standard decentralized identifiers for peer-to-peer relationships.
W3C Verifiable Credentials
Claims made by autonomous agents conform directly to the latest W3C Core Data standard.
SOC2 Type II
Adheres to rigorous automated audit compliance tracks for machine operations.
FREQUENTLY ASKED QUESTIONS
AUTHENTICATE MACHINE FLOWS.
Take control of your automated network operations with cryptographic agent authentication.