Support
Connect Document360
Knowledge base and self-service documentation platform for product and support teams.
Support
Document360
Knowledge base and self-service documentation platform for product and support teams.
API keyScoped proxy
Connect with a provider API key
The client enters their provider key in the hosted connect flow. CybrLink stores it in the credential layer, then agents call through scoped MCP/API access without seeing the raw secret.
Where to get your Document360 API keyStep 1
Open the portal connect flow
Step 2
Enter the provider API key
Step 3
Create a scoped MCP/API key
Sample request
// 1. Mint a session token for the end user
const session = await link.connect.session({
integrationKey: "document360",
userId: "u_42",
});
// 2. After the user enters their provider API key, proxy a request
const res = await link.proxy("document360", "u_42", {
method: "GET",
endpoint: "/api/v1/me",
});More in this category
Document360 + AI agents: common questions
- How do I connect Document360 to an AI agent?
- Create a free CybrLink account, open the dashboard, and click Connect on Document360. You authorize once with an API key; CybrLink stores the credential in its token vault and your agent reaches Document360 through the CybrLink MCP server or the agent proxy API. The credential itself is never placed in the model's context.
- Does Document360 work with Claude, GPT, and other MCP clients?
- Yes. CybrLink exposes a remote MCP (Model Context Protocol) server, so any MCP-capable client or agent framework — including Claude, OpenAI-based agents, and custom agents — can call Document360 once you've connected it. Non-MCP agents can use the authenticated HTTP proxy instead.
- Is it safe to give an AI agent access to Document360?
- CybrLink scopes every connection to the permissions you grant, keeps tokens out of the model, logs each call to an activity audit trail, and lets you revoke the Document360 connection at any time from the dashboard.