# WAMP documentation > WAMP is a general-purpose AI application platform — agents, tools, views, commands, storage, and identity. Everything you build on it is an extension; an app is an extension that owns its window. The hosted execution product, WAMP Cloud, is documented separately at https://docs.cloud.vampikez.fun. This file indexes every page. For the entire corpus as one markdown document, fetch https://docs.vampikez.fun/llms-full.txt. Any single page is also served as its markdown source: append `.md` to its path, for example https://docs.vampikez.fun/build/extensions-and-apps.md. ## Build - [Agents and skills](https://docs.vampikez.fun/build/agents-and-skills/): Ship a configured agent — model, prompt, tool set — and ship skills the model loads on demand when it needs them. - [Extensions and apps](https://docs.vampikez.fun/build/extensions-and-apps/): The anatomy of a WAMP extension — the files on disk, the main and renderer entry points, the activation lifecycle, and what turns an extension into a full app. - [Lifecycle hooks](https://docs.vampikez.fun/build/lifecycle-hooks/): Run your own commands when a chat starts, a prompt is sent, a tool is called, or a native Run finishes. - [The manifest](https://docs.vampikez.fun/build/manifest/): What every field in extension.json means, which ones you set by hand, and the four places where getting one wrong fails quietly. - [Pages and windows](https://docs.vampikez.fun/build/pages-and-windows/): How extension UI reaches the screen — docked pages, app windows, slot views, how a page is routed to, and where your styles actually apply. - [Permissions](https://docs.vampikez.fun/build/permissions/): What each permission in extension.json actually unlocks, which ones the runtime enforces, and why a missing declaration surfaces as undefined rather than as an error. - [The plugin API](https://docs.vampikez.fun/build/plugin-api/): A map of the two API surfaces an extension gets — ctx.api in the main process and pluginAPI in the window — organized by what you are trying to do. - [Portable plugins](https://docs.vampikez.fun/build/portable-plugins/): Install Agent Plugins and Claude or Codex plugin directories as WAMP extensions. - [Scheduled work](https://docs.vampikez.fun/build/scheduled-work/): Schedule agent turns with cron triggers in agent definitions. - [Contributing tools](https://docs.vampikez.fun/build/tools/): Register a function the AI can call — its input schema, its result, how it renders in chat, and what the approval system does with it. - [Typed data](https://docs.vampikez.fun/build/typed-data/): Declare a table schema once and get a typed query API in both halves of your extension, with automatic additive migration when the schema grows. - [Interface kit](https://docs.vampikez.fun/build/ui/): Build a page with @wamp/ui so it inherits the host's components, spacing, type scale, and every theme the user can switch to. ## Examples - [Examples](https://docs.vampikez.fun/examples/): Choose a working extension example by the feature you need, with its host requirements and the guide that owns the complete implementation. ## Identity - [Apps and credentials](https://docs.vampikez.fun/identity/apps-and-credentials/): Every credential a WAMP developer can hold — how to obtain it, its exact header format, lifetime, authority, and how to revoke it. - [Connected resources](https://docs.vampikez.fun/identity/connected-resources/): Let a WAMP extension expose your service to agents as the current organization and user, without another login or copied API key. - [Organizations and roles](https://docs.vampikez.fun/identity/organizations/): How WAMP models accounts, organizations, memberships, invitations, roles, and the fourteen organization permissions that authorize every management call. - [Overview](https://docs.vampikez.fun/identity/overview/): Pick the right WAMP credential for the job — signing a human in, acting for a user from your backend, or acting as your app itself. - [Sign in with WAMP](https://docs.vampikez.fun/identity/sign-in-with-wamp/): Build a working WAMP sign-in — register a client, run authorization code with PKCE, verify the tokens, refresh, and sign out, with a complete relying party you can run. ## Overview - [Build AI applications on WAMP](https://docs.vampikez.fun/): WAMP is a general-purpose AI platform — agents, tools, views, commands, storage, and identity. Build an extension, ship it as a product, or run it behind your own backend. ## Reference - [AI proxy API](https://docs.vampikez.fun/reference/ai-proxy/): Call WAMP's metered AI proxy through the OpenAI-compatible HTTP API with bearer authentication, standard responses, streaming, tools, errors, and usage. - [The wamp CLI](https://docs.vampikez.fun/reference/cli/): Create, develop, validate, and package WAMP extensions from any workspace. - [Manifest reference](https://docs.vampikez.fun/reference/manifest/): Every field in extension.json — type, whether it is required, its default, its constraints, and what it controls. - [Packages and SDKs](https://docs.vampikez.fun/reference/packages/): Every WAMP package, what it is for, who consumes it, and its current availability — with source-checkout and host-provided availability. - [Plugin API reference](https://docs.vampikez.fun/reference/plugin-api/): Every namespace and method an extension can call — ctx.api in the main process and pluginAPI in the window — with the permission each needs and whether it is in the published types. - [Troubleshooting](https://docs.vampikez.fun/reference/troubleshooting/): The WAMP extension failures whose cause is not visible from the symptom — silent empty query results, activation faults, and styling that ignores you. ## Ship - [Branded desktop product](https://docs.vampikez.fun/ship/branded-product/): Configure and build a branded Desktop product, then prepare signed artifacts and a compatible update feed. - [Choosing a path](https://docs.vampikez.fun/ship/choosing-a-path/): Choose between a branded desktop binary and running WAMP behind a product you already operate. - [Your own backend](https://docs.vampikez.fun/ship/own-backend/): Use WAMP as the AI supplier for a product you already run — register an app principal, mint short-lived per-end-user tokens from your own server, and get usage attributed per person. ## Start - [Core concepts](https://docs.vampikez.fun/start/concepts/): The terms you need to choose an extension surface, storage model, agent, and deployment path. - [Quickstart](https://docs.vampikez.fun/start/quickstart/): Create a WAMP extension in your workspace and see it rebuild live in Desktop. - [What WAMP is](https://docs.vampikez.fun/start/what-wamp-is/): Build AI applications from extensions, agent runtimes, tools, views, storage, and identity across WAMP hosts.