Your agent, in your workspace.

Search the Baselumen component catalog by name, slug, description or category. Returns slug, name, category, status, the surfaces each component ships as (html, react, vue, svelte), `free` for the components every plan can fetch, and, for a premium component, its `price` and whether this workspace `owned` it. Fetch source with get_component.

One component's source for a surface. 'html' returns the canonical HTML plus CSS pair; 'vue' and 'svelte' are generated from that same pair; 'react' is the typed React build. A fetch through this tool IS a copy, recorded exactly as copying from the app is. On the Free plan only components marked `free` in search_components can be fetched; Pro and Agency include every component except premium ones, which any plan fetches once the workspace has bought them (owned: true).

The site templates — whole multi-page Astro sites, as opposed to the single components search_components lists. Returns each template's slug, name, tagline, description, accent colour, light/dark tone, its price, whether this workspace owns it, its pages, and how many files and bytes it carries. Templates are sold once per workspace in the Baselumen marketplace; browsing is open to everyone, get_template is the fetch.

One template's complete source tree — every .astro page, the components, the stylesheet, the public SVGs and the project files — as a list of {path, content}, ready to write into a folder. The paths are relative to the template root, so writing them under a directory named for the slug reproduces the project exactly. A fetch through this tool IS a copy, recorded exactly as downloading the zip from the app is. Only templates this workspace owns (owned: true in list_templates) can be fetched, on every plan; the rest are bought once per workspace in the Baselumen marketplace.

The design system's CSS custom properties — colour, type, radius, shadow, motion — read from the canonical stylesheet (src/styles/sl-design-system.css). Baselumen has no separate token API; this stylesheet is the source the whole app draws from, so these values cannot drift from what components render with.

The workspace's own custom components — id, componentId (custom:<uuid>, what pins use), name, category, the library component it was forked from, preview tone and dates. No source; fetch one with get_custom_component.

One custom component with its full markup and css, ready to edit with update_custom_component.

Save a new custom component to the workspace. Markup and css are sanitised on the way in; 256 KB each, 500 components per workspace.

Edit a custom component. Pass any of name, category, previewTone, markup, css to replace them whole, and/or `replacements` for targeted edits: each {in: 'markup'|'css', find, replace} replaces every exact occurrence of `find` and fails if it is absent.

Save a library component as a new custom component (its HTML and CSS, rendered from the library), ready to edit with update_custom_component. It follows the plan as get_component does: the Free plan can fork the free set, and a premium component must be bought first. A fork is not recorded as a copy.

The workspace's Terminal sites — id and name — that components can be pinned to.

The components pinned to a Terminal site's designer shelf.

Push components to a Terminal site: pins them to that site's designer shelf, where the designer can drop them onto pages. Adds to what is already pinned. Accepts library slugs and custom componentIds (custom:<uuid>).

Remove components from a Terminal site's designer shelf. Pages that already use them keep them.

The workspace's design library, most recently touched first: id, name, client, trim size in mm, status and when it changed. No artwork; fetch one with get_design.

One design: its full document (artboard in mm, trim and bleed, every shape) and, unless svg is false, its artwork as SVG. Shape ids here are what edit_design operations name.

The designer's drawing operations — add_shape, update_shape, set_paint, set_type, arrange and the rest — with each one's input schema. edit_design applies a batch of them.

The artboard sizes (business cards, letterhead, logos, social, A-sizes) and the templates a new design can start from.

Start a new design on a preset artboard (blank) or from a template, save it to the library, and return its document. Draw on it with edit_design.

Apply a batch of the designer's operations to a design and save it as one revision — the same edits the designer makes, in the same order. Operations: add_shape, update_shape, set_paint, set_effects, group_shapes, arrange_shapes, combine_shapes, path_command, transform_shapes, set_type, delete_shape, reorder_shape, set_artboard, set_document (schemas from list_design_operations). The batch stops at the first operation that fails, and nothing is saved then. An open designer tab picks the change up when it next loads the design.

Send a design's artwork to a Terminal site's assets. propose (the default) records what would happen and changes nothing; execute writes it.

The push log — what was sent where, proposed or executed, and how it went — newest first.

The workspace's uploaded assets — images and SVGs the designer can place — with their URLs.

The workspace this token belongs to, the token name, its scopes, and its reach (whole workspace or one client). Call this first to learn what the credential may do.

Your profile in the suite — name, handle, headline, bio, job title, location, links, skills and whether it is public.

Update your profile. Pass only the fields to change: fullName, handle, headline, bio, jobTitle, location, pronouns, timezone, links, skills, isPublic. links is merged into the links you have: give a network an address to set it, an empty string to remove it, and leave the rest out to keep them. skills replaces the whole list.

Your settings — theme, density and which emails you receive.

Update your settings. Pass only what changes: theme, compactDensity, emailActivity, emailSupport, emailProduct.

The workspace — name, kind, industry, size, description — and its members with their roles.

Update the workspace's details. Pass only what changes: name, industry, companySize, description.

The workspace's members and pending invitations, with roles.

The workspace's clients — id, name, slug, website, status, industry. A client-scoped token sees only its own client.