The credential proxy your AI agents are running without.

Alter sits at the boundary between your AI agents and every OAuth-protected API they call. It handles token issuance, scope enforcement, rotation, and revocation — without touching your agent code.

How It Works

Alter acts as an OAuth proxy. Agents request credentials from Alter, not from the OAuth provider directly. Alter enforces policies, mints short-lived tokens, and proxies the underlying OAuth flow transparently.

01

Agent credential request

Your AI agent calls alter.io/v1/token with its agent ID and the resource it needs access to. The request includes the requested OAuth scope. No client secrets stored in agent code.

Alter validates the agent identity via a short-lived JWT signed with your deployment's private key.

02

Policy evaluation

Alter evaluates the requested scopes against your YAML policy file. Policies can allow, deny, or downgrade scope claims. A policy that says max_scope: repo:read will strip write access even if the agent requested it.

Policy violations are logged immediately, even when the request is served with a reduced scope.

03

Token issuance and rotation

Alter exchanges your stored long-lived refresh token for a short-lived access token (default TTL: 4 hours, configurable down to 15 minutes). The agent receives only the short-lived token — never the refresh token.

Tokens are automatically revoked at expiry. No manual cleanup scripts needed.

04

Audit log generation

Every token mint, scope grant, and revocation event is written to Alter's immutable audit log. Each entry contains: agent ID, run ID, task description (if provided), OAuth provider, scope granted, TTL, and timestamp.

Logs export to Splunk, Datadog, Elastic, and any webhook endpoint in real time.

05

Emergency revocation

If an agent is compromised or misbehaving, revoke all its active tokens in a single API call or dashboard click. Revocation propagates to all connected OAuth providers within 30 seconds via Alter's revocation API.

Revoke by agent ID, run ID, or OAuth provider — whatever scope you need.

Platform Capabilities

Minimum-Privilege Scope Engine

Define scope policies in YAML. Policies support allow, deny, downgrade, and conditional rules. A rule can say "agent class: data-reader may never receive write access to any provider." Alter enforces this at the proxy layer — the agent's code does not change.

Policy files version-controlled in your Git repo. Alter pulls from your repo on deploy. Changes take effect within 60 seconds without a restart.

Automatic Token Lifecycle

Alter tracks every issued token's TTL and initiates revocation before expiry. Agents get a fresh token on every new task run — there are no long-lived tokens in agent memory, container environment variables, or CI/CD pipelines.

TTL is configurable per agent class, per provider, or globally. Default is 4 hours. Minimum is 15 minutes. Maximum is 24 hours.

Immutable Audit Trail

Audit logs are append-only and cryptographically signed. Each log entry is a JSON object with a SHA-256 hash chained to the previous entry — tampering with any entry breaks the chain and triggers an alert.

Supported export destinations: Splunk HEC, Datadog Logs, Elastic Beats, PagerDuty Events, generic webhook (POST, configurable headers, retry-on-failure).

Zero-SDK Integration

Alter speaks standard OAuth 2.0 (RFC 6749) and OAuth 2.1 (draft). Any agent that can make an HTTP POST request can use Alter without installing a library or modifying its auth flow beyond changing the token endpoint URL.

Native integrations exist for LangChain, AutoGPT, CrewAI, and Dify. Each integration is a one-line config change in the agent's existing setup file.

Multi-Agent Orchestration Support

When a parent agent spawns child agents, Alter propagates the parent's policy constraints to all children automatically. A child agent cannot request scopes the parent is not authorized to delegate. This prevents privilege escalation through agent hierarchies.

Supported orchestration patterns: hub-and-spoke, pipeline chains, and parallel fan-out. Each model is configurable in the policy file.

Credential Vault (Bring Your Own)

Alter never stores your OAuth client secrets in plaintext. It integrates with HashiCorp Vault, AWS Secrets Manager, GCP Secret Manager, and Azure Key Vault for credential storage. If you have an existing vault setup, Alter connects to it — no migration needed.

For teams without a vault, Alter provides an encrypted credential store backed by AES-256-GCM with key rotation every 30 days.

Built for Production Scale

<30ms
Token proxy latency (p99)
10k
Token requests/second (single region)
AES-256
Encryption at rest (GCM mode)
30s
Max revocation propagation time

See it working in your stack

We walk through a live integration with your agent framework in the first call.

Request a Demo View Pricing