Cloud/Create Connector/OpenAPI / Swagger
OpenAPI / Swagger
The third path in Create Connector: connect your API with one URL. Vinkius discovers your endpoints and turns them into tools AI agents can use, with annotations mapped automatically.
OpenAPI / Swagger is the third path inside Create Connector, and it is the fastest one when your API already exists. The console's card says it in one sentence: "Connect your API with one URL. Vinkius discovers your endpoints and turns them into tools AI agents can use." The two tags name the payoff: Auto-generates tools and AI-ready annotations. You do not describe your API, you just point at it.
Deploy Connector
Connect your API to AI agents in under 30 seconds.
Auto-discovers and generates all tools for your AI agents instantly.
Auto-detected from the OpenAPI spec if left empty.
The mockup is the real wizard. Paste a spec URL and watch the detection: the endpoint count lands in emerald while the name and base URL fill themselves. Continue through Security and Governance, then deploy.
One URL. Every tool.
The education panel states the deal: "Paste your spec URL and we do the rest: endpoints discovered, tools generated, annotations mapped. AI agents can use them instantly." The fine print is generous: OpenAPI 2.0, 3.0, 3.1. JSON or YAML. We handle it.
The first step asks for the OpenAPI / Swagger URL. While you type, the console inspects the spec: a blue "Detecting..." spinner runs, then an emerald line announces the result, "{count} endpoints ready for AI". A spec that does not resolve gets the red "Invalid spec URL. Make sure it points to a valid OpenAPI/Swagger file." Before anything is pasted, the field explains itself: "Auto-discovers and generates all tools for your AI agents instantly."
The rest of the form fills itself
Detection does not stop at the endpoint count. The Server Name fills from the spec's title, and its placeholder flips to "Auto-detected ✓". The Base URL is optional because it is "Auto-detected from the OpenAPI spec if left empty." You can override both; the point is that you usually do not have to.
Security: credentials never leave the vault
The second step asks how your API authenticates. The Auth Type options are None · Public API, Bearer Token, Basic Auth (user:password) and Custom Header (with its header name and value). If the spec itself declares a security scheme, a blue banner reports it: "Security detected in spec: Bearer Token. Select below if your API requires it." Whatever you enter carries one promise, written in emerald on the form: "AES-256 encrypted at rest. Credentials never leave your vault." Keys are encrypted at rest, injected at runtime, and invisible to the model; agents call your API through Vinkius, never with your secrets in their context.
Governance: protect what matters
The third step offers two switches, both optional and both editable later from settings:
- Zero-Trust PII Redaction: "Masks emails, SSNs, and credit cards in RAM before returning data to the AI. GDPR-compliant by default."
- Smart Array Truncation, badged Cost Control: "Large arrays shrink automatically. Same data, fewer tokens. Your context window stays focused."
These are the same policies you can manage per connector later in DLP Protection and FinOps Guard; this step just sets the defaults at birth.
The deploy and what comes out
Deploy to Edge runs the swagger phases: parsing the OpenAPI specs, sealing the V8 Isolate Sandbox, injecting Zero-Trust DLP, distributing to the global edge. Then your connector is Live! with its one-time Connection Token and the mcpServers config JSON ready to copy or download, with one tab per client: Claude, Cursor, VS Code, Antigravity and Others. From there it behaves like every connector: Dashboard to watch it, AI Capabilities to review the tools the spec generated, Playground to run them.
Why this path exists
Thousands of APIs already speak OpenAPI. This path turns that existing description into AI Capabilities without writing a line of integration code: one URL in, every endpoint out as a tool an agent can call, annotated and governed from the first request.
What comes next
The last Create Connector path has its own guide: Manual Setup (no spec? add your API by hand, step by step). After the paths, the console's Seller Account covers listing on the marketplace.