Vinkius

The connectivity layer for AI builders.

One Application, unlimited users — each with their own connectors and credentials, isolated and never exposed to Vinkius.

Website · Docs · Cloud · AI Connect

Vinkius turns the AI application you're building into a connectivity platform for your own users. One backend API: each of your users gets their own connectors, their own credentials and their own AI capabilities — and your agents call them from any model runtime. Vinkius handles the connectivity, authentication, permissions, protocols and execution behind those capabilities. Your application identifies the user. That division of labor is the product.

Your users need your AI to act in the real world: open the issue, send the message, query the database, file the ticket. Without a connectivity layer, that means building every integration yourself — OAuth flows per provider, encrypted token storage, protocol handling, API churn, security reviews. Months of plumbing before your product does anything real. Vinkius removes the integration tax: the connectors are built and maintained, credentials are handled with per-user isolation, and the capabilities your agent calls arrive through one API. You compete on your product. The plumbing is done.

• Thousands of connectors from day one — GitHub, Slack, Notion, databases, internal APIs and more, already maintained and growing. You do not build integrations, you do not store tokens, you do not touch OAuth plumbing.
• Per-user isolation — every user connects their own accounts with completely separate connection state, credentials and capabilities. Nothing crosses the boundary.
• Your real users are never exposed to Vinkius — the SDK needs only your opaque external_id. No email, no name, no profile. Vinkius is invisible infrastructure under your product.
• Credentials are write-only — your backend sets them and can verify which fields are configured, but nobody (not your code, not the model, not the dashboard) reads them back.
• Two planes over one credential — control plane (users, connectors, credentials, catalog) and execution plane (capabilities(), execute()) share a single vk_app_sk_* secret.
• Bring your own model runtime — capabilities are framework-neutral JSON Schema objects with OpenAI, Anthropic, Gemini, Vercel AI SDK, LangChain, LlamaIndex and OpenAI-compatible adapters at the model boundary.

Official SDKs for the Vinkius AI Connect platform, one per ecosystem. Same concepts, same two-plane API, same adapters everywhere.

import { Vinkius } from '@vinkius/connect';

const vinkius = new Vinkius({
  appId: process.env.VINKIUS_APP_ID!,
  apiKey: process.env.VINKIUS_APP_KEY!,
});

// give one of YOUR users their own GitHub connection
const user = vinkius.user('alice_123');
const connector = user.connector('github');
await connector.connect();
await connector.credentials.set({ personal_access_token: '***' });

// the executable capabilities available to that user
const capabilities = await user.capabilities({ include: ['github'] });
const created = await capabilities
  .findCapability('Create a new issue in a GitHub repository')
  .execute({ owner: 'acme', repo: 'api', title: 'Broken login flow' });

console.log(created.results?.[0]?.data);

Install: npm install @vinkius/connect · other languages: see the repository table above. Requires a free Vinkius Cloud account.

A connector is not a capability — one connector exposes many capabilities (list repositories, create issue, search code, …). user.capabilities() returns the capabilities available to that user, as executable, framework-neutral objects. An empty result is normal: treat availability as runtime data.

One Application, many users, zero exposure. Per-user isolation, write-only credentials, opaque external identifiers, scoped tokens, and documented guarantees behind every call — see Security and Authentication.

• Docs: vinkius.com/learn/en/connect-sdk
• Cloud dashboard: cloud.vinkius.com
• Issues: open an issue in the SDK repository for your language