vitehub.dev valid
ViteHub
Portable Agents for Vite, built on Server Primitives.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- http://vitehub.dev/llms.txt
- llms-full.txt
- http://vitehub.dev/llms-full.txt
- Sections
- 7
- Links
- 268
- Size
- 47755 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Interface: a documented API or declared MCP endpoint an agent can call
- First seen
- 2026-10-27T10:05:34.182Z
- Last checked
- 2026-10-27T10:05:38.554Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:05:34.187Z. Cached copy · Source on vitehub.dev
# ViteHub
> Portable Agents for Vite, built on Server Primitives.
Rules for coding agents:
- Read the installed package exports and types before you write imports or options. When the installed packages, these docs, and remembered syntax disagree, follow the installed packages.
- Prefer the `vite-hub` distribution: register `vitehub()` from `vite-hub` in the Vite config and import Runtime Helpers from feature subpaths such as `vite-hub/kv`. Some pages use owner packages such as `@vite-hub/kv`; follow the style that the project already uses.
- Keep provider and host selection in the Vite config. Application code calls the same Runtime Helper on every host.
- Give an Agent authority only through Capabilities, Workspaces, Sources, or Channels. Do not pass application secrets or broad access to an Agent implicitly.
- Open the raw page for one feature, such as `https://vitehub.dev/raw/docs/kv.md`, before you write code. Raw pages contain agent-only details that the rendered site does not show. Do not load llms-full.txt for one task.
- Prove the change: run the Runtime Helper, Agent Invocation, webhook, or schedule, and inspect the generated `.vitehub/` state or provider output.
- Install the ViteHub skill for routed guidance: `npx skills add https://vitehub.dev --skill vitehub`.
## Overview
- [ViteHub](https://vitehub.dev/raw/index.md)
## Documentation Sets
- [ViteHub](https://vitehub.dev/llms-full.txt): Server primitives for Vite.
## When to use ViteHub
Use ViteHub when a Vite application needs portable server storage, queues, workflows, schedules, sandboxes, or other Server Primitives; when it needs inspectable Agent Definitions with explicit Capabilities and Workspaces; or when the same runtime behavior must deploy across supported hosts without leaking provider APIs into application code.
- [Choose a ViteHub layer](https://vitehub.dev/raw/docs/getting-started.md): Decide whether the job needs a Server Primitive, an Agent, or both.
- [Install ViteHub](https://vitehub.dev/raw/docs/getting-started/installation.md): Install the framework distribution or a focused owner package.
## ViteHub developer resources
Use these named machine interfaces to inspect ViteHub before reading the full documentation set. ViteHub is installed into your application and does not expose a shared hosted runtime API.
- [ViteHub OpenAPI document](https://vitehub.dev/openapi.json): Discover the public machine-readable resources served by vitehub.dev.
- [ViteHub Agent Skill](https://vitehub.dev/.well-known/skills/vitehub/SKILL.md): Install or inspect the coding-agent instructions and routed references.
- [ViteHub MCP server](https://vitehub.dev/mcp): Connect an MCP client to the Streamable HTTP documentation endpoint.
- [ViteHub CLI on npm](https://www.npmjs.com/package/vite-hub): Install the official CLI included with the vite-hub package.
## Project and trust information
- [About ViteHub](https://vitehub.dev/raw/about.md)
- [Contact ViteHub](https://vitehub.dev
…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 |
|---|---|---|---|---|---|---|---|
| chatbotkit.com | ChatBotKit | interface AI and machine learning AI agents and MCP +2 | US | 56 | ✓ | ||
| agentskit.io | Agents Playbook | documentation AI agents and MCP Developer tools | — | 45 | ✓ | ✓ | |
| agentfield.ai | AgentField | documentation AI agents and MCP Developer tools | US | 53 | ✓ | ✓ | |
| graphed.com | Graphed — Agent Setup Playbook | documentation | US | 47 | ✓ | ||
| wippy.ai | Wippy | documentation AI and machine learning AI agents and MCP +2 | — | 50 | ✓ | ✓ | |
| openvibe.actor | OpenVibe.Actor | interface AI and machine learning AI agents and MCP +1 | — | 45 | ✓ | ✓ | |
| tembo.io | Tembo | interface Infrastructure AI and machine learning +2 | US | 54 | ✓ | ✓ | |
| agentskills.io | Agent Skills | documentation AI agents and MCP Documentation and reference | US | 55 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=vitehub.dev · GET /v1/domain/vitehub.dev · 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 vitehub.dev, 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 vitehub.dev:
1. POST https://agentwebmap.com/v1/sites/vitehub.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://vitehub.dev/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/vitehub.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/vitehub.dev).
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.