@picked/client 0.0.101-next.2 → 0.0.101

package/dist/docs/reference/delivery-api/experience-content.md

@@ -1,152 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Experience Content Endpoint
-
-Fetch the content entries that back the steps of a single experience.
-
-## Request
-
-```
-GET /api/v1/projects/:projectId/experiences/:id/content
-```
-
-| Parameter | In | Description |
-| --- | --- | --- |
-| `projectId` | path | The project the experience belongs to. |
-| `id` | path | The experience to fetch content for. |
-| `preview_token` | query | Optional. With it, the endpoint returns preview content, which is unpublished. |
-
-## Response
-
-```json
-{
-  "experienceId": "exp_123",
-  "versionId": "ver_456",
-  "content": [
-    {
-      "id": "entry_789",
-      "contentModelKey": "page-hero",
-      "data": {
-        "title": "Spring sale",
-        "category": { "contentEntryId": "entry_42", "contentModelKey": "category" }
-      }
-    }
-  ],
-  "references": [
-    {
-      "id": "entry_42",
-      "contentModelKey": "category",
-      "data": { "name": "Outerwear" }
-    }
-  ]
-}
-```
-
-| Field | Type | Description |
-| --- | --- | --- |
-| `experienceId` | `string` | The experience the content belongs to. |
-| `versionId` | `string \| null` | The published version id, or `null` on preview. |
-| `content[]` | `array` | The entries that the steps of the experience point at. |
-| `content[].id` | `string` | The content entry id. |
-| `content[].contentModelKey` | `string \| null` | The Key of the Model, or `null` when it cannot be resolved. |
-| `content[].data` | `object` | The entry data. It matches the schema of the Model. |
-| `references[]` | `array` | Every entry that a `reference` field reaches, in the same blob shape as `content[]`. |
-
-The published response and the preview response hold the same fields, and the same
-values, for the same content.
-
-## A reference field points at a separate blob
-
-A [Reference field](/reference/dashboard/content/models#reference-fields) arrives as a
-pointer, and not as the entry:
-
-```json
-{ "contentEntryId": "entry_42", "contentModelKey": "category" }
-```
-
-A repeatable Reference field arrives as an array of such pointers.
-
-The entry itself arrives in `references[]` under its own `id`. Look the pointer up
-there. The SDK does this for you, through
-[`useReference` and `getReference`](/reference/sdk/content).
-
-`references[]` holds each entry one time, for any number of fields that point at it. It
-omits the entries that are in `content[]` already.
-
-### What `references[]` omits
-
-Picked resolves a chain of references to a maximum depth of 5. It counts the depth from
-the entries in `content[]`. An entry is absent from `references[]` when Picked cannot
-resolve it:
-
-| Cause | Result |
-| --- | --- |
-| The target was deleted | The pointer stays. The entry is absent. |
-| The target is in another workspace | The pointer stays. The entry is absent. |
-| The chain makes a cycle | The pointer stays. The entry is absent. |
-| The chain is deeper than 5 | The pointer stays, with its `contentModelKey`. The entry is absent. |
-
-A pointer with no entry in `references[]` means that there is no such entry. Picked sends
-no empty blob for it.
-
-:::warning
-A reference pointer also carries a `data` field with the content of the target inlined.
-This is for the SDK versions that came before `references[]`. Read `references[]`
-instead. A later release removes the inline copy.
-:::
-
-## An HTML asset comes back in the response
-
-A Model can have an [HTML asset](/reference/dashboard/content/asset-library) field. The
-value of that field arrives inside the response. The endpoint changes the reference to
-`{ id, content }`. There, `content` holds the HTML that you uploaded, as a string. It
-is `null` when the endpoint cannot resolve it:
-
-```json
-{
-  "id": "entry_789",
-  "contentModelKey": "page-hero",
-  "data": {
-    "markup": { "id": "asset_42", "content": "<section>...</section>" }
-  }
-}
-```
-
-The SDK renders the inlined HTML directly, with no extra storage fetch.
-
-## Status codes
-
-| Code | Meaning |
-| --- | --- |
-| `200` | Success. |
-| `401` | Invalid `preview_token`. |
-| `404` | The experience has no published content. |
-
-## Example
-
-```bash
-curl https://api.picked.app/api/v1/projects/proj_123/experiences/exp_123/content
-```
-
-```json
-{
-  "experienceId": "exp_123",
-  "versionId": "ver_456",
-  "content": [
-    { "id": "entry_789", "contentModelKey": "page-hero", "data": { "title": "Spring sale" } }
-  ],
-  "references": []
-}
-```
-
-## Related
-
-- [About the two APIs](/explanation/the-two-apis)
-- [About content references](/explanation/content-references) — why a reference is a pointer.
-- [Content](/reference/sdk/content) — how the SDK resolves a pointer.
-- [Project config](/reference/delivery-api/project-config) — the endpoint that links a step to an entry.
-- [Server Snapshot](/reference/sdk/ssr/serialize) — how the SDK reads this content.
-- [Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling)

package/dist/docs/reference/delivery-api/index.md

@@ -1,45 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Delivery API
-
-The Delivery API is a public REST API. It is read-only, and it serves the published
-configuration of your project together with your page content. It is separate from the
-GraphQL management API.
-
-## Base URL and versioning
-
-All Delivery API routes are versioned under `/api/v1`:
-
-```
-https://api.picked.app/api/v1
-```
-
-## Published content and preview content
-
-Each endpoint serves two surfaces:
-
-- **Published** content is anonymous. Anybody can read your published configuration and
-  your published content.
-- **Preview** content needs a `preview_token` query parameter. With it you can render
-  an unpublished draft before you make it live.
-
-The management API holds the preview token of a workspace in the `previewToken`
-field. The preview action in the dashboard also makes one for you.
-
-## Endpoints
-
-| Endpoint | Description |
-| --- | --- |
-| [Project Config](/reference/delivery-api/project-config) | `GET /api/v1/projects/:projectId` returns the published configuration of the project, with the content link of each step. |
-| [Experience Content](/reference/delivery-api/experience-content) | `GET /api/v1/projects/:projectId/experiences/:id/content` returns the Content Entries of an experience. |
-
-Both endpoints share some behaviour. See
-[Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling).
-
-## Related
-
-- [About the two APIs](/explanation/the-two-apis) — which one to use, and why they are
-  separate.

package/dist/docs/reference/delivery-api/preview-caching-crawling.md

@@ -1,79 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Preview, cache, and crawlers
-
-Both Delivery API endpoints share this behaviour: the preview token, the cache, CORS,
-and what a crawler can read.
-
-## Preview tokens
-
-Pass `?preview_token=<token>` to read unpublished content. Both endpoints take it,
-and both return `versionId: null` for a preview. An invalid token returns `401`.
-
-```bash
-curl "https://api.picked.app/api/v1/projects/proj_123?preview_token=<token>"
-```
-
-The [management API](/tutorials/first-api-call) holds the preview token of a workspace in the
-`previewToken` field. The preview action in the dashboard also makes one for you.
-
-Use the same token for the project configuration request and for the experience content
-request. Both then come from the same preview.
-
-## Cache
-
-The cache rules depend on the surface and on the client that makes the request. The
-SDK sends a `Picked-Client: sdk` request header:
-
-| Request | `Cache-Control` |
-| --- | --- |
-| Published, `Picked-Client: sdk` | `public, s-maxage=10` |
-| Published, other clients | `private, no-store` |
-| Preview | `no-store` |
-
-A published response that a cache can hold also sends `Vary: Picked-Client`. A shared
-cache therefore keys on the client header. It never gives a body that it cached for
-the SDK to a request from another client.
-
-## CORS
-
-Both endpoints can be read from another origin. An `OPTIONS` preflight returns `204`
-with the CORS headers:
-
-| Header | Value |
-| --- | --- |
-| `Access-Control-Allow-Origin` | `*` |
-| `Access-Control-Allow-Methods` | `GET, OPTIONS` |
-| `Access-Control-Allow-Headers` | `Content-Type, Picked-Client, Picked-Version, traceparent, tracestate` |
-
-## Crawlers and search rank
-
-A crawler can read both endpoints, so a search engine can read your published
-content. A preview URL is disallowed, so a draft never reaches the index. These are
-the `robots.txt` rules:
-
-```
-User-agent: *
-
-# Let a crawler read the public project configuration and experience content.
-Allow: /api/v1/projects
-Allow: /api/v1/projects/*/experiences/*/content
-
-# Keep a preview response, which is a draft, away from a crawler.
-Disallow: /api/v1/projects/*preview_token=
-
-# Everything else stays disallowed: GraphQL, MCP, internal routes, and the ping.
-Disallow: /
-```
-
-See [Project Config](/reference/delivery-api/project-config) and
-[Experience Content](/reference/delivery-api/experience-content) for the endpoints.
-
-## Related
-
-- [About the two APIs](/explanation/the-two-apis) — how a preview stays out of the search
-  index.
-- [How to render an unpublished preview](/how-to/render-an-unpublished-preview)

package/dist/docs/reference/delivery-api/project-config.md

@@ -1,65 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Project Config Endpoint
-
-Fetch a project's published configuration: its experiences, steps, and the link from each step to the Content Entry that backs it.
-
-## Request
-
-```
-GET /api/v1/projects/:projectId
-```
-
-| Parameter | In | Description |
-| --- | --- | --- |
-| `projectId` | path | The project to fetch config for. |
-| `preview_token` | query | Optional. With it, the endpoint returns the preview configuration, which are unpublished. |
-
-## Response
-
-The response carries the project's experiences and steps. Each step includes `layoutContentId`, the reference to the Content Entry that backs that step's layout. Use it to know which experiences have content to fetch from the [Experience Content](/reference/delivery-api/experience-content) endpoint.
-
-| Field | Type | Description |
-| --- | --- | --- |
-| `id` | `string` | The project id. |
-| `versionId` | `string \| null` | The published version id, or `null` on preview. |
-| `steps[].layoutContentId` | `string \| null` | The Content Entry of this step, or `null` when the step has no content. |
-
-## Published content and preview content
-
-For published content, `versionId` holds the ID of the published version. For preview
-content, which you read with `?preview_token=...`, `versionId` is `null`, because
-there is no published version. See [Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling).
-
-## Example
-
-```bash
-curl https://api.picked.app/api/v1/projects/proj_123
-```
-
-```json
-{
-  "id": "proj_123",
-  "versionId": "ver_456",
-  "steps": [
-    {
-      "id": "step_1",
-      "key": "hero",
-      "name": "Hero",
-      "layoutName": "HeroLayout",
-      "layoutContentId": "entry_789"
-    }
-  ]
-}
-```
-
-Pass the config to `serialize()` on your server to produce an SSR snapshot. See [Server Snapshot](/reference/sdk/ssr/serialize).
-
-## Related
-
-- [About the two APIs](/explanation/the-two-apis)
-- [Experience content](/reference/delivery-api/experience-content)
-- [How to server-render a page](/how-to/server-render-a-page)

package/dist/docs/reference/delivery-api/workspace-schema.md

@@ -1,107 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Workspace Schema Endpoint
-
-A JSON Schema document for the structure of your project: content models, fields, feature keys, experience keys, and step keys. Tooling reads this endpoint to generate TypeScript types for your application.
-
-## Request
-
-```
-GET /api/v1/projects/:projectId/schema
-```
-
-| Parameter | In | Description |
-| --- | --- | --- |
-| `projectId` | path | The project whose schema to fetch. |
-| `preview_token` | query | Optional. Returns the preview (unpublished) schema when you send it. |
-
-## Response
-
-The response is a [JSON Schema draft 2020-12](https://json-schema.org/draft/2020-12/schema) document with Picked-specific extension fields:
-
-| Field | Description |
-| --- | --- |
-| `x-picked-schema-version` | Schema document version (currently `1`). |
-| `x-picked-source` | `"published"` or `"preview"` — mirrors the surface you requested. |
-| `x-picked-version-id` | Published workspace version id, or `null` on preview. |
-| `x-picked-step-content-models` | Map of step key → content model key, which gives each layout its type. |
-| `x-picked-step-fields` | Map of step key → the keys of the fields on that step, in order. |
-| `x-picked-feature-values` | Map of feature key → the values that the feature can serve. Picked adds this field only when the workspace has a Text feature flag. |
-| `x-picked-workflow-action-keys` | Keys of the actions that start a workflow, sorted. Picked adds this field only when the workspace has such an action. |
-| `$defs.contentModels` | JSON Schema definitions for each content model. |
-| `$defs.contentBlocks` | JSON Schema definitions for reusable content blocks. |
-| `$defs.fields` | Object schema for project field values. |
-| `$defs.featureKeys` | String enum of feature keys. |
-| `$defs.experienceKeys` | String enum of experience keys. |
-| `$defs.stepKeys` | String enum of step keys. |
-| `$defs.actionKeys` | String enum of action keys. A schema from a version that Picked published before this field existed has none. |
-
-## Field values
-
-Each content model and content block definition describes a field value in the form that
-the Delivery API serves it:
-
-| Field type | Value |
-| --- | --- |
-| `asset` | One of two objects. A resolved asset has `id`, `url`, `mimeType`, `sizeBytes`, `fileName`, `width`, and `height`. `width` and `height` are `null` for a file that is not an image. An asset that does not exist, or that you deleted, has `id`, and `versionId` when the reference holds a version. |
-| `html-asset` | `id` and `content`. `content` is the text of the file, or `null` when Picked cannot read the file. |
-| `content-block` | One of the block definitions in `$defs.contentBlocks` that the field accepts: a `$ref`, or a `oneOf` of `$ref`s. A field with a category accepts the blocks of that category. A field with no category accepts all blocks. Each block definition has `contentBlockId`, `contentBlockKey`, and `data`. `contentBlockKey` is a `const` that holds the key of the block. |
-| `reference` | `contentEntryId`. The value can also have `contentModelKey` and `data`. It has `data` only when the API resolves the entry. A reference that is too deep, or that makes a cycle, can have `contentModelKey` and no `data`. |
-
-The Delivery API does not serve a block that no longer exists, for example a block that you
-deleted. A repeatable `content-block` field does not include the block in its list. A
-`content-block` field that is not repeatable is not in the `data` of the entry.
-
-A published schema keeps the value shapes that it had when you published the workspace.
-The preview schema always has the shapes in this table.
-
-## Published and preview
-
-On the published surface, the schema reflects your last published workspace. On the preview surface (`?preview_token=...`), the schema reflects the current draft workspace. See [Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling).
-
-When no published schema exists, the published endpoint returns `404` and tells you to publish the workspace.
-
-A Boolean feature flag serves `true` or `false`, and it contributes no entry to
-`x-picked-feature-values`. A workspace of Boolean feature flags therefore omits the field.
-A schema that Picked published before Text feature flags existed also omits it.
-
-Picked sorts the values of each Text feature flag by the key of the variant. The document
-therefore does not change when you rename a variant or move a row.
-
-## Example
-
-```bash
-curl https://api.picked.app/api/v1/projects/proj_123/schema
-```
-
-```json
-{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "$id": "picked:project/proj_123/schema",
-  "x-picked-schema-version": 1,
-  "x-picked-source": "published",
-  "x-picked-version-id": "ver_456",
-  "x-picked-step-content-models": {
-    "intro": "welcome-page"
-  },
-  "x-picked-feature-values": {
-    "hero": [false, "hero-a", "hero-b"]
-  },
-  "$defs": {
-    "contentModels": {},
-    "contentBlocks": {},
-    "fields": { "type": "object", "additionalProperties": false, "properties": {} },
-    "featureKeys": { "type": "string", "enum": ["default", "hero"] },
-    "experienceKeys": { "type": "string", "enum": ["welcome-survey"] },
-    "stepKeys": { "type": "string", "enum": ["intro"] }
-  }
-}
-```
-
-## Related
-
-- [Type generation](/reference/sdk/type-generation) — Generate TypeScript types from this schema in your app.
-- [Project Config](/reference/delivery-api/project-config) — Runtime project configuration for the SDK.

package/dist/docs/reference/glossary.md

@@ -1,201 +0,0 @@
----
-type: reference
-layout: docs
----
-
-# Glossary
-
-Every term that Picked uses, and what each one means. The dashboard, the API, and the SDK
-sometimes use different words for the same thing. This page gives the word that the
-documentation uses, and it names the others.
-
-## Accounts and access
-
-| Term | What it is |
-| --- | --- |
-| **Organization** | The top level. It holds your projects, your members, and your settings. You can belong to more than one. |
-| **Member** | A person in an organization. Each member holds one role. |
-| **Role** | What a member can reach. It decides whether a member can create a project, edit an experience, or read a report. |
-| **API key** | A credential for a server-to-server integration. It belongs to an organization, it can belong to one project, and it carries scopes. |
-| **Scope** | One permission, written `resource/action`, such as `organization/read`. A scope decides which operations a caller can do. |
-| **Session** | The result of a sign-in. It holds an access token, a refresh token, and the time at which the access token expires. |
-| **User** | A person who signs in to the Picked dashboard. A user is not a visitor. |
-| **Invitation** | An offer to join an organization, sent to an email address. It waits until the person accepts it. |
-| **MFA factor** | A second credential on an account, such as a telephone number. |
-
-## Projects and versions
-
-| Term | What it is |
-| --- | --- |
-| **Project** | One site or one application. Each project has its own experiences, content, and configuration. |
-| **Project configuration** | The published settings of a project: its experiences and steps, and the content link on each step. The Delivery API serves it, and the SDK reads it. The SDK parameter is `projectConfig`. |
-| **Workspace** | One version of the configuration of a project. You hold a change in a workspace, see a preview of it, and publish it. |
-| **Draft** | A workspace that no visitor sees. |
-| **Live** | The workspace whose snapshot the SDK serves. Each project has exactly one. |
-| **Archived** | A draft that you put to one side. It is still editable, and it is out of the default list. |
-| **Version** | An immutable snapshot of a workspace, made when you publish. The **Publish history** page lists them. |
-| **Preview** | A view of an unpublished workspace on your own site. It reaches your browser only. |
-| **Preview environment** | A named target that a preview opens against. |
-| **Project settings** | The settings of one project, which you edit in the dashboard. These are not the project configuration that the Delivery API serves. |
-
-## Experiences
-
-| Term | What it is |
-| --- | --- |
-| **Experience** | Personalized content that Picked serves to a visitor. It is a Flow or a Page. |
-| **Flow** | An interactive experience of more than one step, which the browser renders. |
-| **Page** | A standalone experience that your server renders from a content entry, for content that a search engine must read. |
-| **Step** | One screen that a visitor sees. It holds fields. |
-| **Field** | A data input inside a step. It collects a name, an email address, a preference, or a choice. |
-| **Field option** | One choice in a field that has a fixed set of choices. Each option carries a value, and it can carry a condition. |
-| **Action** | A side effect that starts when the flow reaches it. Your application registers a handler for it. |
-| **Condition** | A rule that decides whether a visitor sees something, or which branch a flow takes. |
-| **Predicate** | A function that you register on the client, so a condition can read data that only your application holds. |
-| **Response** | A value that a visitor sends through a field. |
-| **Origin** | The node where every flow starts. |
-| **Node** | One part of a flow on the canvas: an origin, a step, an action, or a condition. |
-| **Handle** | A connection point on a node. An input handle is on the left, an output handle on the right. |
-| **Key** | The stable identifier of a step, a field, an action, or a condition. Your application and your API calls both use it. You set it one time, and you cannot change it. |
-| **Layout name** | The name of the component that renders a step, such as `card` or `modal`. |
-| **Target** | The element that an experience renders against, found by its target selector. |
-
-## Feature flags
-
-| Term | What it is |
-| --- | --- |
-| **Feature flag** | A control that decides which visitors see a change, so you can run an A/B test or release in stages. The API type is `Feature`. |
-| **Weight** | The percentage of visitors that Picked allocates to a feature flag, from 0 to 100. |
-| **Allocation** | The act that puts a visitor in a feature flag. It happens when something first reads the bucket. |
-| **Bucket** | The value a feature flag resolves to for one visitor. |
-| **Exposure** | The moment a visitor enters a test. It is the same moment as the allocation. |
-| **Version** | A number on a feature flag that forms part of the cache key. It is not part of the allocation. |
-
-## Content
-
-| Term | What it is |
-| --- | --- |
-| **Model** | A reusable schema that sets which fields a piece of content can hold. The API type is `ContentModel`. The dashboard lists them under **CMS**, at **Models**. |
-| **Block** | A reusable schema fragment that you put inside one or more Models. The API type is `ContentBlock`. The dashboard lists them under **CMS**, at **Blocks**. |
-| **Content entry** | One instance of a Model, filled with real values. The dashboard lists them under **CMS**, at **Content entries**. |
-| **Category** | The role of a Model or a Block. It is fixed when you create the record. |
-| **Page layout** | A Model with the Page layout category. It sets which fields a Page can hold. |
-| **Step layout** | A Model with the Step layout category. It sets which fields one Step inside a Flow can hold. |
-| **Section** | A Block with the Section category. A **Page Sections** field accepts it. |
-| **General content** | A Model or a Block with no category. It has no layout role, and nothing renders its entries directly. |
-| **Reference** | A field that points one content entry at another. The pointer holds the id of the target, and not a copy of it. |
-| **Target Model** | The Model whose entries a Reference field accepts. It holds a Key. **Any Model** sets no limit. |
-| **Entry title** | The name that the entries list shows. It is the first single-line text field of the entry, and it falls back to the entry id. |
-| **Asset** | A file that your content points at: an image, a video, a document, or HTML. |
-| **Asset library** | The project-level store that holds your assets. |
-| **Design system** | A set of shared design decisions for a project. |
-| **Content schema** | The set of fields that a Model or a Block defines. |
-| **Asset version** | One file that somebody uploaded for an asset. The library keeps the earlier versions. |
-| **Validation error** | A report that one field in a content entry does not match its schema. It carries the path to the exact field. |
-
-## Leads
-
-| Term | What it is |
-| --- | --- |
-| **Lead** | One set of answers that a visitor gave to a flow. It belongs to the project, and it stays after you publish a new version. |
-| **Response** | One answer in a lead, held under the key of the field that asked for it. |
-| **Label** | A name and a value that you or a workflow puts on a lead, a project or a workflow run. A label on a lead sits outside the answers, and it stays when you change your fields. A label can expire. Refer to [Labels](/reference/dashboard/labels). |
-| **Label owner** | The lead, the project or the workflow run that has a label. The owner sets the scopes that read and write the label. |
-| **Namespace** | The first part of the name of a label, which groups related keys, such as `details` in `details.phone`. |
-| **Label type** | How to read the value of a label: text, number, boolean, or JSON. |
-| **Visit** | The events one visitor made in one session. The API calls it `session`. |
-| **Capture event** | The analytics event that recorded the capture of a lead. |
-
-## Workflows
-
-| Term | What it is |
-| --- | --- |
-| **Workflow template** | Text with `{{ … }}` in a node of a workflow. Picked fills it with data from the run. Refer to [Workflow templates](/reference/dashboard/workflow-templates). |
-| **Run variable** | A value that each node of a run can read, such as `run.startedAt` or `current.visit`. |
-
-## The SDK
-
-| Term | What it is |
-| --- | --- |
-| **Client** | The object that `createClient()` returns. It holds your configuration and runs the experiences. |
-| **Plugin** | A piece of behaviour that you pass to the `plugins` array of the client. |
-| **Component name** | The identifier that points an experience at a component in your application. |
-| **Adapter** | The function that lets the client render a framework component: `adaptReactComponent` or `adaptSvelteComponent`. |
-| **Slot** | A named mount point, rendered by `<ExperienceSlot name="…" />`. It maps to the `.picked-slot-<name>` selector. |
-| **Placement** | Where an experience renders against its target: `replace`, `before`, `prepend`, `append`, or `after`. |
-| **Target selector** | The selector that an experience renders into. |
-| **Content index** | The store of every content record that the client holds, keyed by id. `useContent(id)` and `useReference()` read it. |
-| **Snapshot** | The plain JSON that `serialize()` returns on your server, and that seeds the client in the browser. |
-| **Precondition** | A gate that decides whether Picked starts at all. |
-| **Visitor** | The person on your site. Picked gives each one a stable ID. A visitor is not a user. |
-| **Framework plugin** | The plugin that lets the client render a React or a Svelte component. |
-
-## APIs and analytics
-
-| Term | What it is |
-| --- | --- |
-| **Delivery API** | The public, anonymous, read-only REST API that serves your published configuration and content. |
-| **Management API** | The authenticated GraphQL API that controls your projects, experiences, and content. |
-| **Preview token** | A token that lets a Delivery API request read unpublished content. |
-| **PickedQL** | The SQL query language for your Picked analytics data. |
-| **Virtual table** | A table name in PickedQL, such as `metrics`, that maps to the real tables below it. |
-| **Virtual function** | A short function in PickedQL, such as `control_users()`, that expands to a full aggregate expression. |
-| **Dimension** | A column that PickedQL joins for you, such as `device_category`. |
-| **Report** | An embedded analytics dashboard or question, attached to a project. |
-
-## Tools
-
-| Term | What it is |
-| --- | --- |
-| **MCP connection** | A link between a Picked project and an AI tool, over the Model Context Protocol. The dashboard calls this **MCP connections**. |
-| **Integration** | A connection between Picked and another service. |
-| **Tag ID** | The identifier of a project, which the template for Google Tag Manager uses. |
-
-## Verbs
-
-The actions that Picked names, and what each one does. Where an API mutation uses the
-word exactly, the table says so.
-
-### You act on the dashboard
-
-| Verb | What it does |
-| --- | --- |
-| **Create** | Makes a new record. |
-| **Update** | Changes a record that exists. |
-| **Delete** | Removes a record permanently. You cannot reverse it. |
-| **Publish** | Makes an immutable snapshot of a workspace and serves it to your visitors. |
-| **Archive** | Moves a draft workspace out of the default list. It stays editable. |
-| **Unarchive** | Returns an archived workspace to the default list. |
-| **Duplicate** | Copies a workspace, and everything in it, into a new draft. |
-| **Restore** | Moves the live pointer of a project to an earlier version. It changes no data. |
-| **Preview** | Opens your site with an unpublished workspace applied, for your browser only. |
-| **Invite** | Sends an invitation to join an organization. |
-| **Revoke** | Invalidates an API key or an invitation immediately. |
-| **Install** | Connects an integration to your project. |
-
-### Picked acts on a visitor
-
-| Verb | What it does |
-| --- | --- |
-| **Allocate** | Puts a visitor in a feature flag. |
-| **Resolve** | Gives a feature flag its bucket for one visitor. The first read resolves it. |
-| **Decide** | Runs the `decide` function of a feature flag. |
-| **Evaluate** | Runs a condition against the current state. |
-| **Invoke** | Calls a predicate from inside a condition. |
-| **Serve** | Sends published content to a visitor. |
-
-### Your code acts on the SDK
-
-| Verb | What it does |
-| --- | --- |
-| **Register** | Adds a component, an action, a predicate, or a feature flag to the client. |
-| **Start** | Runs the client. `start()` is idempotent. |
-| **Adapt** | Wraps a framework component so the client can render it. |
-| **Serialize** | Builds a snapshot on your server, with `serialize()`. |
-| **Seed** | Gives the client a snapshot, so the first render matches the server. |
-| **Hydrate** | Takes over the server markup in the browser. |
-| **Render** | Puts a component into the page. |
-
-## Related
-
-- [About how Picked works](/explanation/how-picked-works) — how these parts fit together.
-- [Projects](/reference/dashboard/projects) — the dashboard surface.