Components catalog

An answer is one to three components from a closed catalog of 13. The agent picks the components and fills their fields; it cannot invent a fourteenth, cannot emit HTML, and cannot write a URL. Every component is validated against its schema on the server before a single byte reaches the visitor, and a component that fails validation is dropped while the rest of the answer still arrives.

The 17 components

Component	When the agent picks it
`heading`	To open a multi-component answer with a title and one framing line. Never the whole answer.
`media`	One image or video, when seeing it is the answer (“what does it look like”, “show me”).
`mediaCard`	One idea explained in copy with a supporting image beside it.
`gallery`	Two to five images side by side: a tour, a comparison, a set of spaces.
`timeline`	A step sequence: a process, an onboarding, a journey.
`accordion`	Secondary detail on one theme the visitor did not ask for: fine print, deep dives. Renders collapsed.
`cta`	A next-step banner when the answer ends in one clear action.
`metrics`	One to three headline figures about the business, taken from its own material.
`grid`	A mixed set of cells for a rich overview when a flat list would fall short.
`faq`	Several distinct questions at once, phrased the way a visitor would ask them.
`stats`	Third-party figures with their attribution, for “why does this matter”.
`leadForm`	A contact form, when the visitor wants to be contacted.
`info`	Last resort: nuance, an honest “no, but here is what we do”, an off-topic redirect.
`features`	A set of 2–6 equal, icon-led cards: an inventory, the reasons behind a claim, options, use cases, a closed comparison.
`chips`	Compact groups of short labels (channels, integrations, methods): names, not explanations.
`logos`	Social proof or integrations shown as brand marks, optionally grouped.
`plans`	The business’s real pricing offers as cards; the server formats every price, the model only picks which offers to show.

Rules that apply to every component

Text fields carry no HTML, no URLs and no markdown. The only exception is the body of info, which allows markdown formatting but still refuses HTML, raw URLs and inline links.
References are ids, never addresses. assetId names an image in your registry, actionId names one of the actions you declared on the page, linkId names one of your approved links. Ids are lowercase with single hyphens or underscores, a shape a URL cannot match. The server swaps each id for the real value after validation.
Icons come from a fixed vocabulary of generic names (shield, clock, truck, message-circle, …). They are interface vocabulary, not your data, so they are a closed list.
At most one instance of each component per answer.

Props, component by component

heading

Prop	Type	Notes
`title`	text, 4–80	A 2–5 word label naming what follows.
`description`	text, 8–220, nullable	One complete sentence framing it.

media

Prop	Type	Notes
`title`	text, 4–80, nullable	Optional short label.
`assetId`	asset id	One image or video from the page’s registry.
`caption`	text, 8–160, nullable	One sentence saying what the visitor is looking at.

Landscape assets only. A portrait one belongs in mediaCard, where it fits without stretching.

mediaCard

Prop	Type	Notes
`title`	text, 4–80	Label.
`description`	text, 16–300	One or two complete sentences carrying the substance.
`assetIds`	1–2 asset ids	Images that show what the text says.
`cta`	`label` (2–32) + `actionId`, nullable	Only when a next step genuinely helps.

gallery

Prop	Type	Notes
`title`	text, 4–80, nullable	Optional label.
`variant`	`grid` or `bento`	`grid` for a uniform square comparison; `bento` for a tour that keeps each image’s proportions.
`items`	2–5 entries	Each: `assetId` plus an optional `caption` (4–120).

timeline

Prop	Type	Notes
`title`	text, 4–80	Label for the sequence.
`orientation`	`horizontal` or `vertical`	Horizontal when each step carries an image, vertical for compact icon steps.
`items`	2–6 steps	Each: `title` (2–80), `description` (8–160), `assetId` (nullable), `icon` (nullable).

accordion

Prop	Type	Notes
`title`	text, 4–80	The theme being broken down.
`items`	2–6 rows	Each: `label` (2–80) and `body` (16–400), plain text.

Rows of one theme, hidden until the visitor clicks, so the accordion carries secondary detail only. Content that answers the actual question goes to grid, timeline, metrics, faq or info; visitor-phrased questions belong in faq.

cta

Prop	Type	Notes
`eyebrow`	text, 2–48, nullable	An optional small line above the title.
`title`	text, 4–80	Label.
`description`	text, 8–180	One sentence about what the visitor gets.
`primaryCta`	`label` (2–32) + EITHER `actionId` (continues the chat) OR `linkId` (opens a page)	The action. Labels are verbs.
`secondaryCta`	same shape, nullable	Only when a real alternative exists.

metrics

Prop	Type	Notes
`title`	text, 4–80	Label.
`items`	1–3 figures	Each: `value` as displayed (1–16 chars, e.g. `6`, `24/7`), `label` (8–160), `assetId` (nullable).

Only figures that appear literally in your material. Third-party numbers belong in stats, where they carry a source.

grid

Prop	Type	Notes
`title`	text, 4–80	Label.
`items`	2–6 cells	Each: `size` (`large` or `small`), `title` (2–80), `description` (8–160), `icon` (nullable), `assetId` (nullable).
`cta`	`label` + one destination, nullable	The single next step when the overview ends in one.

faq

Prop	Type	Notes
`title`	text, 4–80	Label.
`items`	2–5 pairs	Each: `question` (8–120) and `answer` (16–300).

stats

Prop	Type	Notes
`title`	text, 4–80	Label.
`items`	2–4 figures	Each: `value` (1–12, e.g. `5x`, `32%`), `label` (8–160), `source` (2–60).

Both the number and its attribution must exist in the material. An attribution is never dropped or altered.

leadForm

Prop	Type	Notes
`title`	text, 4–80	Label.
`description`	text, 8–180	What happens after they leave their details.
`formId`	form id	One of the forms you configured; the server resolves its fields, and the agent never sees what a visitor types.

The agent chooses which form to show; you own its fields and where a submission goes. A form submits internally (stored and emailed to you) or externally (posted to your own API), and only an external form may include a password — wondeya never stores one.

features

Prop	Type	Notes
`title`	text, 4–80	Label for the set.
`items`	2–6 cards	Each: `icon` (from the enum), `title` (2–80), `description` (8–160).
`cta`	`label` + one destination, nullable	The natural next step.

chips

Prop	Type	Notes
`groups`	1–3 groups	Each: a `label` (1–3 words) and 1–6 `items`, each with a short `label` and an optional `icon`.
`cta`	`label` + one destination, nullable	Only when a next step genuinely helps.

logos

Prop	Type	Notes
`title`	text, 4–80	Label.
`logoIds`	2–8 logo ids	Brand marks from your logo set; never invented.

plans

Prop	Type	Notes
`offerIds`	the offers to show	You configure the offers; the server renders the real names, prices and buttons. The model never writes a figure.
`note`	text, nullable	An optional one-liner about the selection, never a figure.
`linkId`	nullable	An optional “see all plans” link.

info

Prop	Type	Notes
`title`	text, 4–80	Label.
`body`	markdown, 16–600	The complete answer. Formatting yes; HTML, raw URLs and inline links no.
`bullets`	1–6 lines (2–160 each), nullable	For enumerations.
`links`	1–3 entries, nullable	Each: `label` (2–48) and `linkId` from your approved links.
`cta`	`label` + `actionId`, nullable	Only when a next step genuinely helps.

How the catalog is enforced

The same schema contract is enforced by the server before anything streams and mirrored by the client’s renderer registry. That registry is closed: a component type it does not recognise is never guessed at (the visitor sees a short note asking them to refresh the page instead), and a component whose image fails to load degrades to a neutral placeholder instead of a broken box. Because the catalog is closed and its text fields refuse markup, the worst outcome of a malicious instruction hidden inside uploaded knowledge is a component that fails validation and disappears, not markup on your visitor’s screen.

Get Started

Build Your Page

Add It To Your Site

Under The Hood

Trust

Components catalog

The 17 components

Rules that apply to every component

Props, component by component

heading

media

mediaCard

gallery

timeline

accordion

cta

metrics

grid

faq

stats

leadForm

features

chips

logos

plans

info

How the catalog is enforced

​The 17 components

​Rules that apply to every component

​Props, component by component

​heading

​media

​mediaCard

​gallery

​timeline

​accordion

​cta

​metrics

​grid

​faq

​stats

​leadForm

​features

​chips

​logos

​plans

​info

​How the catalog is enforced

The 17 components

Rules that apply to every component

Props, component by component

heading

media

mediaCard

gallery

timeline

accordion

cta

metrics

grid

faq

stats

leadForm

features

chips

logos

plans

info

How the catalog is enforced