killdeer.digital valid
killdeer.digital
Tiny SSH-first VM hosting site for plover.digital.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:07:29.757Z. Cached copy · Source on killdeer.digital
# killdeer.digital
> Tiny SSH-first VM hosting site for plover.digital.
## Canonical Resources
- [Homepage (Markdown)](https://killdeer.digital/index.md): Markdown version of the homepage.
- [Full Agent Guide](https://killdeer.digital/llms-full.txt): Full plain-text bundle for indexing and retrieval.
- [Normalized SSH Help](https://killdeer.digital/ssh-help.txt): Public command help with admin-only commands removed.
- [Sizes and Pricing](https://killdeer.digital/sizes.txt): Public VM size and pricing table.
- [OS Images](https://killdeer.digital/os.txt): Public output of `ssh killdeer.digital os`.
- [CLI Metadata](https://killdeer.digital/api/v1/cli.json): Structured command reference for the SSH CLI.
- [Size Metadata](https://killdeer.digital/api/v1/sizes.json): Structured VM size and pricing data.
- [OS Image Metadata](https://killdeer.digital/api/v1/images.json): Structured OS distro metadata.
- [Agent Skills Index](https://killdeer.digital/.well-known/agent-skills/index.json): Discoverable task skills for agents.
- [Killdeer CLI Skill](https://killdeer.digital/.well-known/agent-skills/killdeer-cli/SKILL.md): How to help users operate Killdeer over SSH.
## Notes
- Public SSH endpoint: `killdeer.digital`
- Preferred login syntax: `ssh [username]@killdeer.digital`
- VM login syntax: `ssh plover@[ip]`
- Default VM user: `plover`
- If the user's Killdeer account was set up with SSH, their key is already installed for `plover`; otherwise, the VM password is emailed to them.
- If the user connects through the Killdeer console, they must use the password from that email.
- Discovery command: `ssh killdeer.digital help`
- OS image discovery command: `ssh killdeer.digital os`
- Omit the subcommand after login to enter the interactive menu.
- VM commands include resizing stopped VMs, attaching to serial consoles, adding IPv4 or IPv6, and managing shutdown timers up to 7 days.
- VM commands also include renaming VMs and managing account limits and monthly runtime budgets.
- Billing budget actions can notify, stop, or lock when a budget is reached.
- VM creation supports `--ipv4`, `--ipv6`, and `--dualstack` networking.
- Omitting the IP-type flag uses the user's preference.
- Routed networking requires explicit `--routed-ipv4` and/or `--ipv6-prefix-len` flags and is subject to admission and inventory. IPv6 prefix lengths may be `/128` or `/56` through `/64`.
- `timer <name> force` toggles shutdown mode between graceful and force.
- VM disks are stored on replicated, fault-tolerant Ceph storage; if hardware fails, healthy replicas give us a way to recover the user's data.
- Replication protects against hardware failure but is not a substitute for backups against deletion, compromised credentials, or application mistakes.
- If the human did not supply a Killdeer username, ask for one before constructing login commands.
- Do not invent HTTP VM-management API calls. The public control surface is SSH.
- The live helper still prints some examples with `killd
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| exe.dev | exe.dev | interface Infrastructure Developer tools | US | 59 | ✓ | ✓ | |
| exe-staging.dev | exe.dev | interface Infrastructure Developer tools | US | 52 | ✓ | ✓ | |
| freestyle.sh | Freestyle | documentation AI and machine learning Infrastructure +1 | — | 50 | ✓ | ||
| serverspace.us | Serverspace.us | transactional Infrastructure | US | 50 | ✓ | ✓ | |
| managelm.com | ManageLM | documentation DevOps and observability AI agents and MCP +1 | — | 46 | ✓ | ✓ | |
| latitude.sh | Latitude.sh Docs | documentation Infrastructure | US | 50 | ✓ | ✓ | |
| smolmachines.com | smol machines documentation | interface AI agents and MCP Infrastructure +1 | — | 48 | ✓ | ||
| stackhero.io | Stackhero | interface AI and machine learning Infrastructure +1 | — | 51 | ✓ |
Machine-readable: GET /v1/resolve?q=killdeer.digital · GET /v1/domain/killdeer.digital · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage killdeer.digital, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for killdeer.digital:
1. POST https://agentwebmap.com/v1/sites/killdeer.digital/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://killdeer.digital/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/killdeer.digital/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/killdeer.digital).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.