Pilvio MCP integration for AI agents.
Connect AI agents to Pilvio through 5 structured actions, including get billing account, get current user, and list billing accounts. Review authentication…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Pilvio integration exposes
The Pilvio Agent App exposes 5 provider-backed actions for developer tools and storage work. Its current contract lets an authorized agent get one pilvio billing account by numeric identifier, get the authenticated pilvio user profile, and list pilvio billing accounts attached to the authenticated user. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Pilvio account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Pilvio capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_billing_accountREADGet one Pilvio billing account by numeric identifier.
INPUTS: billingAccountId
get_current_userREADGet the authenticated Pilvio user profile.
list_billing_accountsREADList Pilvio billing accounts attached to the authenticated user.
INPUTS: showShadow
list_locationsREADList Pilvio data center locations available for resource operations.
list_virtual_machinesREADList Pilvio virtual machines, optionally scoped to a documented location slug.
INPUTS: locationSlug
INPUT CONTRACTS
Know what the action needs before it runs.
get_billing_account
billingAccountIdOPTIONAL- The Pilvio billing account identifier.
list_billing_accounts
showShadowOPTIONAL- Whether to request deleted billing accounts with show_shadow.
list_virtual_machines
locationSlugOPTIONAL- The optional Pilvio location slug to use after /v1 in the API URL.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Billing Account
Get one Pilvio billing account by numeric identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_billing_accountVerify with Get Current User
Get the authenticated Pilvio user profile. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Pilvio with explicit limits
- Authorize Pilvio with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Pilvio data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Pilvio rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Pilvio task completed successfully.
CONNECTION MODEL
API key
Pilvio API token sent in the apikey header. Register or manage API tokens at https://app.pilvio.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Pilvio.