Provenance
- Archive digest
- sha256:df3164579d85faba45c8cb5217a40823a766c3f1e2063d59e98581510be92504
- Report digest
- sha256:0e586aaae3613f31be6fea3f615ff08a608385d58fa976c54a9bdc01651b2bad
- Attestation
- signed (DSSE)
- Signing key
- -_Ea_eEb6AVt8DSP
agentry verify blaktron/vultr-setup-wizard@0.3.0
Check the key id against the registry's published set at /.well-known/agentry/signing-keys.json. A signature proves who built this release, not that its contents are safe.
Manifest
The manifest as the registry validated and stored it, in canonical JSON.
{
"name": "vultr-setup-wizard",
"tags": [
"vultr",
"cloud",
"infrastructure",
"security",
"setup"
],
"guide": {
"task": "e.g. Set up a two-tier web app with PostgreSQL for users in Frankfurt, domain example.com, within my stated monthly budget.",
"connect": {
"VULTR_API_KEY": "Optional: enable API access in the Vultr Console under Account → API, or use a dedicated organization user under Manage Organization → Users → API Access. Connect the key through the run's credential controls. Grant only the resource-management permissions needed for the agreed setup, plus read access for inventory and catalog checks. Restrict API access to actual runner outbound IP ranges when your operator provides them; your home IP may differ. Without a key, the wizard produces portal instructions and an unverified deployment plan instead of making changes. Never paste the key into chat."
},
"prepare": [
"Know your workload, users' locations, monthly budget and availability needs.",
"Optionally connect a Vultr API key through the run's credential controls, not chat.",
"Have your SSH public key and administrative source IP ranges ready.",
"Have your domain and access to its registrar if you want DNS configured.",
"Have a payment method available for signup; enter it only on Vultr."
],
"overview": "An interactive wizard for Vultr signup and project-specific infrastructure: private networking, restricted firewalls, SSH-key access, compute, managed databases and DNS. With a connected API key it makes explicitly approved changes; without one it gives portal instructions. It documents resources, costs, pending work and verification limits; guest configuration and credential handling remain your responsibility."
},
"modes": [
"interactive"
],
"intake": [
{
"id": "vultr_api_key",
"type": "secret",
"prompt": "Optional Vultr API key for making approved changes; leave blank for portal instructions."
}
],
"license": "MIT",
"publish": {
"include": [
"agent.yaml",
"AGENT.md",
"README.md",
"LICENSE"
]
},
"runtime": {
"interfaces": [
"claude-skill",
"agents-md"
]
},
"summary": "Guides Vultr signup and project-specific infrastructure setup, makes approved API changes, and documents results.",
"version": "0.3.0",
"namespace": "blaktron",
"entrypoints": {
"instruction": "AGENT.md"
},
"interactive": {
"opening": "I'll help you plan and set up a Vultr environment, confirming costs and access changes before acting. What are you building, where are your users, and what monthly budget should we work within? A connected API key lets me make approved changes; otherwise I'll guide you through the Console."
},
"capabilities": {
"exec": "none",
"network": {
"egress": [
"api.vultr.com"
]
},
"secrets": [
"VULTR_API_KEY"
],
"dataAccess": [
"other"
],
"filesystem": {
"read": "none",
"write": "none"
},
"optionalSecrets": [
"VULTR_API_KEY"
]
},
"schemaVersion": "2"
}