Agent Access Manager by AethosHub
PricingRequest a demo

Change the endpoint. Keep the SDK.

Integration is a base URL and a credential. Everything else — routing, policy, metering, and evidence — is configuration inside the gateway rather than code inside your applications.

Setup

Three steps to a governed model call.

Administrators do this once. After that, onboarding a new application is issuing a key.

Step 01Connect your model providers

Register customer-owned provider credentials and define the model aliases approved for application use.

Step 02Issue scoped access

Give every application, agent, team, or project a revocable virtual key with model, budget, rate, and guardrail policy context.

Step 03Route, enforce, and investigate

Applications call one gateway endpoint. Agent Access Manager authorizes and routes requests, enforces policy, and records governed activity.

Integration

The same client code, pointed at your gateway.

Because the gateway speaks the OpenAI shape, the OpenAI SDK, the Anthropic SDK, LangChain, and coding agents such as Claude Code and Codex all connect without an application rewrite.

PythonTypeScriptGocurlAny OpenAI-compatible client
shell — a governed call
curl https://gateway.acme.com/v1/chat/completions \
  -H "Authorization: Bearer sk-aam-…" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "fast",
    "messages": [{"role":"user","content":"Hello"}]
  }'

# 200 OK  — routed, screened, metered, recorded
# 429     — budget or rate limit reached
# 403     — blocked by a guardrail policy
The request pipeline

What happens inside a single call.

Five stages run on every governed request. A denial at any stage returns a clear status to the caller and is recorded like any other outcome.

  1. 01
    AuthenticateResolve the virtual key, owner, team, and scope
    IDENTIFIED
  2. 02
    AuthorizeEvaluate key scope, provider, and model access
    ALLOWED
  3. 03
    InspectApply guardrails, budgets, and rate policy
    ENFORCED
  4. 04
    RouteForward through a configured model deployment
    ROUTED
  5. 05
    RecordCapture policy decisions, usage, cost, and outcome
    AUDITED
What changes

From shared secrets to governed access.

Before

Shared vendor keys in application config

  • One provider key copied across services, notebooks, and agent runtimes
  • Rotation means a coordinated change across every consumer
  • Spend visible only as a single vendor invoice, after the fact
  • No record of which application or team made which call
  • Prompt and response content leaves with no inspection

After

Scoped virtual access through one gateway

  • Each application, agent, and team holds its own revocable key
  • Revoke one consumer without touching the vendor credential
  • Budgets and rate limits enforced before the call is forwarded
  • Every call recorded with identity, model, tokens, cost, and outcome
  • Guardrails inspect and redact in both directions, streaming included

Step-by-step integration guides, configuration reference, and the full API surface are in the documentation.

Walk through it against your own stack.

We will take one of your existing applications, point it at a gateway, and show the governed call, the policy decision, and the audit record it produces.

Read the docsRequest a demo

We typically respond within one business day.