01
Token separation
Durable OAuth tokens stay in your credential layer. Agents never hold them; CybrLink keeps them out of the model runtime entirely.
OAuth, token custody, and app access for AI agentsGive agents app access.
Give agents app access.
Keep tokens out of the model.
CybrLink is the control layer between your agents and user-connected apps. Run it with a credential layer you control so OAuth tokens stay in your infrastructure while agents get scoped, auditable access to 544 integrations.
- App integrations
- 544
- Tokens in the model
- 0
- Calls audited
- 100%
The catalog
544 apps you can plug your agents into.
OAuth and API-key apps — connect once, and agents call them through one scoped key. Credentials never touch the model.
A few lines of Python. Your agent is connected.
Install the SDK, mint a session, and route agent tool calls through a credential layer you control. Every one of the 544 integrations uses the same call shape — and the provider token never reaches the model.
$pip install cybrlink
- One SDK call to mint a scoped session — no OAuth plumbing.
- Tokens never enter the model; the agent only holds a short-lived session.
- Same call shape for all 544 integrations — no per-provider glue code.
# pip install cybrlink
import os
from cybrlink import CybrLink
link = CybrLink(api_key=os.environ["CYBRLINK_API_KEY"])
# 1. Mint a scoped, short-lived session for one of your end users.
session = link.sessions.create(user_id="u_42")
# 2. Your agent calls a connected app through CybrLink. The user's
# OAuth token stays in your infrastructure — the model only ever
# sees this scoped session, never the credential itself.
inbox = link.proxy(
provider="google-workspace",
session_token=session.token,
method="GET",
endpoint="/gmail/v1/users/me/messages",
)
for message in inbox["messages"]:
print(message["id"])You bring the credential layer. CybrLink makes it safe to hand to an agent.
Self-hosting a vault (we support Nango today) gets you token storage. It does not get you a safe way to point an autonomous agent at it — that's the layer CybrLink adds.
02
Policy & per-user scoping
Every agent call is checked against the user, integration, and permission set it's allowed to use.
03
Agent gateway
One controlled API for tool access, connection state, and revocation, so agents never talk to the vault directly.
04
Audit trail
A reviewable record of which user, key, integration, endpoint, method, outcome, and failure reason each agent action produced.
Security & compliance
Enterprise-grade security, audited to the standards your buyers ask for.
Type II
SOC 2
Security, availability, and confidentiality controls, independently audited.
Certified
ISO 27001
A formal information-security management system across the platform.
Compliant
GDPR
EU data-protection and privacy rights, with data-processing agreements available.
- Tokens held in infrastructure you control — never in the model
- Encryption in transit and at rest
- Append-only, tamper-evident audit log
- Least-privilege, per-user scoped access
6 agent workflows with scoped app access.
Each recipe shows the apps, scopes, and starter prompt an agent needs — without asking for broader access than the workflow requires.
Email Agent
Triage the inbox, draft replies, ship follow-ups. Reads & writes across mailboxes with scoped auth.
Calendar Agent
Books, reschedules, holds prep blocks. Sees free/busy across team calendars with read-only fallback.
Code Agent
Watches deploys, incidents, and database health. Turns production signals into scoped operational action.
Build with custody from day oneConnect every app your agent needs.
Connect every app your agent needs.
Keep credentials out of the prompt.
Start with the catalog and connect flow. Pair CybrLink with your controlled credential layer when you are ready to keep token storage under your own control.