> ## Documentation Index
> Fetch the complete documentation index at: https://docs.webstorio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# References overview

> Lookup for the Webstorio Website API, Client SDK, CLI commands and configuration, and MCP tools.

These pages are **reference** material — exact options, methods, and tools. For guided learning, use [Documentation](/) (dashboard) or [Developer](/developer) (CLI and agents).

## Where to look up

<CardGroup cols={2}>
  <Card title="CLI commands" icon="square-terminal" href="/cli/commands">
    Every `webstorio` command and option.
  </Card>

  <Card title="CLI configuration" icon="settings" href="/cli/configuration">
    Full `webstorio.config.ts` schema.
  </Card>

  <Card title="Client SDK" icon="braces" href="/api-reference/sdk/overview">
    `window.webstorio` methods on published sites.
  </Card>

  <Card title="MCP tools" icon="bot" href="/api-reference/mcp/overview">
    Tool catalog for the remote MCP server.
  </Card>

  <Card title="Supported libraries" icon="package" href="/api-reference/supported-libraries">
    Packages you can import in page code.
  </Card>
</CardGroup>

## Website API

Use these APIs on **published websites** — the sites your visitors see at `my-site.webstor.io` or your custom domain. Page code calls `window.webstorio` methods, and the SDK talks to your site's public API behind the scenes.

All website API traffic uses your **published site origin** — the URL visitors already use:

* `https://my-shop.webstor.io` (Webstorio subdomain)
* `https://www.yourdomain.com` (custom domain)

The client SDK calls this origin automatically. You do not configure a base URL in page code.

### Resources

Which resources are available depends on your enabled [website features](/guides/website-features):

| Feature             | Resources                          |
| ------------------- | ---------------------------------- |
| Content & CMS       | Content types, entries, categories |
| Form & Survey       | Form schemas and submissions       |
| Online Store        | Products, cart, orders             |
| User Authentication | Sign-in, session, sign-out         |
| App Data            | Custom table records               |

Writes (forms, orders, App Data creates) may require a signed-in visitor session.

Prefer the **client SDK** in generated page code — it handles requests, cookies, and feature checks for you. If you use `fetch` directly, send requests to the same origin as the page (your subdomain or custom domain).

## SDK reference

| Guide                                   | Topics                               |
| --------------------------------------- | ------------------------------------ |
| [Overview](/api-reference/sdk/overview) | Runtime, feature gates, method index |
| [CMS](/api-reference/sdk/cms)           | Content types, entries, categories   |
| [Forms](/api-reference/sdk/forms)       | Schema, submit, public submissions   |
| [Store](/api-reference/sdk/store)       | Products, cart, orders               |
| [Auth](/api-reference/sdk/auth)         | Sign-in, session, sign-out           |
| [App Data](/api-reference/sdk/app-data) | Custom tables CRUD                   |

Setup guides: [Content & CMS](/guides/content-and-cms) · [Forms](/guides/forms) · [Online store](/guides/online-store) · [User Authentication](/guides/user-authentication) · [App Data](/guides/app-data)