private.me Quickstart
Get AutoGPT xLink
PRIVATE.ME · Quickstart Guide

AutoGPT + xLink

Add identity-based M2M authentication to AutoGPT agents in 3 lines of code. Replace API keys with cryptographic agent identities. Zero token management, cascading failure elimination, 603× faster authentication.

3-line integration Zero config 0.36ms auth overhead 603× speedup
Step 01

Installation

Install the AutoGPT xLink integration package via npm:

Terminal
# Install via npm
npm install @private.me/autogpt-xlink

# Or via pnpm
pnpm add @private.me/autogpt-xlink

# Or via yarn
yarn add @private.me/autogpt-xlink
COMPATIBILITY
Works with AutoGPT v0.5.0+ and all AutoGPT forks. Requires Node.js 18+ or Bun 1.0+. Zero additional dependencies.
Step 02

Basic Usage

Replace API keys with cryptographic agent identities in three lines:

Python (AutoGPT Agent)
from autogpt.agent import Agent
from autogpt_xlink import XLinkAuth

# Create agent with xLink identity authentication
agent = Agent(
    name="research-agent",
    auth=XLinkAuth(
        service="analytics",
        scope=["read:reports", "write:insights"]
    )
)

# Agent automatically authenticates via DID identity
# No API keys, no tokens, no credential rotation
result = await agent.send_message(
    to="analytics-service",
    payload={"query": "Q4 revenue trends"}
)
WHAT JUST HAPPENED?
XLinkAuth generated a cryptographic DID identity for your agent (Ed25519 keypair). When the agent sends a message, xLink creates a signed envelope with service name + scope + nonce. The receiving service validates the signature against its trust registry. No API keys stored, no tokens to expire, no OAuth flows.
Step 03

Multi-Agent Coordination

AutoGPT agents with xLink identities can coordinate securely without centralized auth:

Python (Multi-Agent System)
from autogpt.agent import Agent
from autogpt_xlink import XLinkAuth, TrustRegistry

# Initialize trust registry (shared across all agents)
registry = TrustRegistry()

# Research agent: read-only access
research = Agent(
    name="research-agent",
    auth=XLinkAuth(
        service="knowledge-base",
        scope=["read:documents"],
        registry=registry
    )
)

# Analysis agent: read + write access
analysis = Agent(
    name="analysis-agent",
    auth=XLinkAuth(
        service="knowledge-base",
        scope=["read:documents", "write:insights"],
        registry=registry
    )
)

# Agents coordinate via identity, not API keys
docs = await research.fetch("recent-papers")
insights = await analysis.process(docs)
await analysis.save(insights)
603×
Faster Auth
0.36ms
Auth Overhead
73.4%
E2E Speedup
Zero
Token Failures
Benefits

Why xLink for AutoGPT?

1. Cascading Failure Elimination

The Problem: One expired OAuth token can restart 500 AutoGPT agents simultaneously. Token refresh failures cascade across your entire agent fleet.

xLink Solution: Agent identities never expire. No tokens to refresh, no credentials to rotate. Cascades cannot happen because there's no central authentication dependency.

2. Zero Credential Management

Traditional AutoGPT: Store API keys in environment variables, rotate periodically, manage access across hundreds of agents, handle credential leaks.

With xLink: Each agent generates its own cryptographic identity on startup. No shared secrets, no key storage, no rotation schedule.

3. Scope-Based Access Control

AutoGPT agents declare capabilities via scopes (e.g., read:reports, write:insights). Services validate scopes against trust registry. Fine-grained permissions without OAuth complexity.

4. Redo Multiplication

Measured Impact: 2,000 AutoGPT agents restarting after OAuth failure spend 91 hours repeating work (cascading task resets). With xLink: 6 hours (authentication never fails). 15× reduction in wasted compute.

Step 04

Configuration Options

Customize xLink behavior for your AutoGPT deployment:

Python (Advanced Configuration)
from autogpt_xlink import XLinkAuth, TrustRegistry

# Initialize trust registry with custom options
registry = TrustRegistry(
    backend="redis",        # or 'memory', 'file'
    ttl=3600,               # Cache trust decisions for 1 hour
    audit_log=True           # Enable audit logging
)

# Create agent with custom auth configuration
agent = Agent(
    name="production-agent",
    auth=XLinkAuth(
        service="payments",
        scope=["read:transactions", "write:invoices"],
        registry=registry,
        nonce_window=300,      # 5-minute replay protection window
        sign_all=True,          # Sign every message (default: true)
        verify_all=True         # Verify every incoming message
    )
)
PRODUCTION CHECKLIST
Before deploying to production: (1) Use persistent trust registry backend (Redis/PostgreSQL, not in-memory), (2) Enable audit logging for compliance, (3) Configure nonce window based on network latency (300-600 seconds typical), (4) Set up monitoring for signature verification failures.
Step 05

Trust Registry Setup

The trust registry maps agent identities to authorized services and scopes:

Python (Trust Registry Management)
from autogpt_xlink import TrustRegistry

registry = TrustRegistry()

# Register agent identity with allowed services
registry.register(
    agent_did="did:xlink:agent:research-001",
    services={
        "knowledge-base": ["read:documents"],
        "analytics": ["read:reports", "write:insights"]
    }
)

# Verify agent has required scope
is_authorized = registry.verify(
    agent_did="did:xlink:agent:research-001",
    service="knowledge-base",
    scope="read:documents"
)  # Returns: True

# Revoke access (instant, no credential rotation needed)
registry.revoke(
    agent_did="did:xlink:agent:research-001",
    service="analytics"
)

Key Advantage: Revocation is instant. With API keys, you must rotate credentials across all agents. With xLink, update the trust registry entry — access revoked immediately, no agent restarts required.

Next Steps

Learn More

SUPPORT
Questions? Email contact@private.me for technical support, integration assistance, or enterprise licensing.