Skip to main content
Use Pilvio through Corsair: one client, typed API calls. Authenticate with an API token created in the Pilvio user interface; the plugin sends it in the apikey header. Every call goes against https://api.pilvio.com/v1. Most write endpoints take form-encoded bodies; SSH keys and firewalls take JSON, and the plugin handles both. Answers are bare JSON objects or arrays; business errors carry {“errors”: {“Error”: …}}, and authentication failures answer 403. Location-scoped resources live under /v1/{slug}/… with the slug from config.listLocations (cyc01, bus02, …); without a slug the API serves the default location. Lists answer whole arrays with no pagination. Deletes and reinstalls are destructive: vm.reinstall replaces the VM’s operating system and storage.disks.delete / storage.buckets.delete / network.*.delete remove the resource. Networks can only be deleted when empty and not the default. The API documents more resources than this plugin covers (VM replicas, clones and backups, disk attach, floating IPs, load balancers, payments and invoices), all on the same shapes. Every operation is described in the official docs served at https://api.pilvio.com. What you get:
  • 40 typed API operations

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

List locations
Create a VM
See the full list on the API page.

What’s next

API reference

Every pilvio.api.* operation with input and output types.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.