Atoms / Library

Content library

126 published atoms, grouped by topic. Each one is assembled for the right visitor at the right moment.

Also available as machine-readable JSON for LLMs and agents: /api/content

feature74 atoms

The answer where the question is asked

A growing share of buying research never touches your website. Someone asks an assistant what tools exist, what they cost, and which one fit

Install Spectare directly from the WordPress plugin directory

Everything Spectare does on WordPress travels through one plugin, and the plugin is now in the official WordPress plugin directory. Go to Pl

Every workspace gets its own ChatGPT connector URL

Spectare speaks the Model Context Protocol, and every workspace now has its own dedicated connector endpoint at spectare.ai/api/mcp/{orgSlug

Warm cache hits land in about 50ms even on a first visit

Spectare's cold-build path used to mean a 10 to 20 second wait before the largest paint on a fresh intent. Mint-time warming closes that gap

Long-lived context tokens for ABM outreach with stated segments

When a personalised link is built for an email campaign or an account-based outreach sequence, the one-hour default token lifetime is nearly

Spectare works inside your agents with three MCP tools

If your product includes an AI assistant, chatbot, or agentic workflow, Spectare can be added as a native tool. Any agent that supports the

Ask a question and watch the page assemble right here

The homepage now has a live question input sitting directly under the assembly claim. Type any question about Spectare and a personalised pa

Give one atom per page a visual lift with the emphasis toggle

Every atom on an assembled page competes for a visitor's attention, and sometimes you know which one should win. The atom editor now has an

Tell Spectare which zones your page places

The SSR assembly endpoint accepts a zones array in the request body. Pass the zone names your page actually renders, for example ["hero", "c

Your content becomes machine-readable on publish

Spectare handles machine readability automatically. The moment you publish an atom, it becomes part of a clean, structured content feed that

AI assistants can send visitors to your best content

When an AI assistant wants to send a user to your site, it can ask Spectare what page would be most relevant for that specific person. Spect

Server-rendered personalisation on warm cache hits

Spectare solves the flash-of-default-content problem that plagues most personalisation platforms. When a cached assembly exists for your vis

Personalisation coverage across your entire site

Spectare's server-rendered personalisation approach now covers your homepage, features overview, AI and analytics sub-pages, integration pag

AI assistants need your readable content

More of your buyers start their research by asking an AI assistant rather than typing into a search engine. When that happens, the assistant

Unanswered visitor questions appear verbatim in your gaps feed

When a visitor types a question into Spectare's ask surface and the library answers it weakly, that question now appears verbatim in the Gap

Silent intent detection plus explicit visitor input

Spectare works out who each visitor is the moment they arrive, without asking anything. It reads the referrer, UTM parameters, the page they

Editing an atom restarts the evidence window from scratch

Spectare holds every variant's conversion rate as a confidence interval rather than a single number, and names a winner only when the interv

Conversions credit every atom in the journey not just the last page

When a visitor browses three pages before converting, the content that caught their attention on page one has always done real work. Until n

Exploration rate starts adaptive and greys out in learning mode

The exploration rate slider in Workspace Settings has always accepted 0, but the label used to say 'Off', which was wrong. Setting the rate

What's Working ranks variants by shrunk rate not raw conversion rate

The What's Working panel in the Spectare admin shows you which content variants are performing across your audiences and funnel stages. The

Images and text now explore and exploit as one treatment

Spectare uses a multi-armed bandit algorithm to select images. Each image in your library can be tagged with audience affinities and buying-

Assembly orders the page as an argument when atoms carry roles

When atoms carry a rhetorical role, the Spectare assembly engine now orders the page as a structured argument rather than leaving sequence t

Headless delivery and zone-aware assembly work together

Spectare now surfaces two related capabilities on its features page: headless delivery and zone-aware assembly. Headless means the assembly

Announcement atoms are now listed on the atoms page

The announcement atom type is now part of the documented atom library on the Spectare atoms page, alongside feature, pricing, case-study, fa

Zone overrides set in Spectare now work on WordPress

Until plugin 1.9.0, zone overrides configured in your Spectare workspace had no effect on WordPress pages. The plugin resolved zones by matc

Component contracts are now mechanically enforced

Every component in the Spectare registry can now carry a typed contract that the assembly engine verifies after the AI returns. The contract

Browse every component live in the product nav

The Spectare component library is now a first-class destination in the Product menu. Previously it was only reachable through the demo landi

This page was chosen for you

Spectare runs on Spectare. The site you are reading is a customer of the product it sells, and the sections that vary on it are filled the s

Conversions credit the content shown

Owning a website commercially means being asked what it did this quarter, and most analytics answer a slightly different question. You can s

Atom types match your industry

Spectare ships with a default set of seven atom types and three funnel stages tuned for B2B and SaaS sites. If your organisation is in retai

Preview any persona's page

The Spectare admin includes a Persona tab on the preview page. Choose an audience, a funnel stage, and a content type, and you instantly see

One landing page, every campaign

When you run campaigns to different audiences (developers, marketing managers, startup founders), you normally need a separate landing page

No wrapper elements required

Spectare now fills your existing HTML elements directly. Add a data-spectare-target attribute to any heading, paragraph, or anchor you alrea

Dynamic at static speed

Spectare answers repeat visitors from cache. Once an intent pattern has been assembled, everyone who arrives the same way is served the stor

Exploration favours the rarer hero

Spectare tests different atom arrangements automatically. Set an exploration rate in Settings and a share of visitors will see an experiment

A starter library from your website

When you create a Spectare workspace, you can provide your existing website URL and Spectare will read your real content and turn it into dr

Spectare discovers your best page layouts automatically

Spectare treats the arrangement of components on a page as a separate variable from the content inside them. Your atoms stay exactly as you

Audit your library in admin

The Spectare admin includes a set of library management tools that help you keep your content performing well over time. The Library audit g

See exactly what Spectare personalised and why

Spectare has a visitor-facing transparency overlay that shows anyone on your site exactly what has been personalised for them and why. Appen

Component eligibility at a glance

Spectare now lets you decide exactly which content components are allowed to appear on your site, and you can narrow or widen that control b

When visitors check for fit

Spectare has added a dedicated intent type for visitors who are checking whether the platform suits their stack, team, or use case. Previous

The returning visitor log

When a returning visitor arrives, Spectare reads a visit log stored in their browser localStorage and passes it to the classifier as a signa

What changes when your website answers people individually

Your website says one thing to everyone. That is not a design failure, it is arithmetic: one page, many audiences, and whoever writes it has

A product page per shopper

Two people open the same product page for completely different reasons. One is buying a present and cares whether it arrives wrapped and in

Launch a personalised campaign without involving engineering

With most personalisation tools, adding a new audience variant means a ticket to engineering, a new page in the CMS, and a two-week wait. Sp

The REST API flow

The Spectare API follows a three-step flow: qualify, assemble, and convert. POST to /api/qualify/{orgSlug} with a summary string describing

Your homepage treats everyone alike

A venue has audiences that want genuinely different things from the same page. A family with young children needs to know about the trail, t

Every visitor gets a different experience

Most websites show every visitor the same thing. A product marketer lands on your homepage and gets the same experience as a software engine

Every session re-qualifies from scratch

Client-side personalisation re-qualifies on every session, so a returning visitor is always treated as a fresh signal. Campaign visitors a

Visitor qualification stores patterns, not visitors

During visitor qualification, traits are derived from the signal pattern itself, not from any visitor identifier. If two visitors arrive wi

Images, text and CTAs optimised together

Spectare treats images and text as separate, interchangeable modules. When a visitor arrives, the engine independently selects the best text

Hero zones never render empty

Spectare now guarantees that your hero zone always carries a call-to-action, regardless of whether you have uploaded a hero image. When a he

Conversion attribution shows which content atoms actually converted

Most personalisation tools tell you which page variant won. Spectare tells you which specific pieces of content drove the conversion, not ju

Brand voice control

Spectare lets you define exactly how Spectare's AI should write. Set your brand voice once in Settings and it applies to every headline and

Write copy in your own voice not ours

Spectare writes and assembles content on your behalf, but your brand has a voice that is entirely its own. Brand Voice lets you set a plain-

Your own llms.txt as a structured entry point

When an AI assistant reads your site, it does not browse fifty pages the way a person would. It fetches what looks like a map, then follows

Install once, hand over the keys

Spectare separates the developer's job from the marketer's. Your team sets up the integration and the atom library; the client's marketers t

One brand colour everywhere

The React package now accepts an accent prop on ComponentRenderer, PersonalisedSection, and the server renderer. Pass a single hex value and

The block that adapts per visitor

The Spectare Zone block is a native Gutenberg block. Find it in the block inserter, drag it onto any page, choose the zone name, and publish

Patterns cached, people never

Visitor identity is never stored. Session signals such as referrer URL, UTM parameters, and the page they landed on are used to classify int

Every conversion event teaches Spectare what works

Spectare brings real conversion history into every page assembly decision. When the AI selects which content atoms to show a visitor, it wei

Every client site, one platform

Each client gets their own Spectare workspace: separate atoms, separate audience segments, and separate analytics. Your team has access to a

See which personalisation components are actually reaching visitors

The Spectare admin audit page has a Component Spread panel showing exactly which personalisation components are rendering for real visitors.

Multiple audiences can be selected per atom

A marketer can assign multiple audiences to an atom. This allows the intent classification to accept any segment name you define. A retail

No page-per-variant to maintain, per client

The old way to personalise is to build and maintain a separate page for every audience, which multiplies the work with every client you take

Your library as clean JSON

Spectare exposes every published atom as clean JSON at GET /api/content. A bare request with no credentials returns the Spectare library. A

Show each client which content actually converted

Spectare records which atom, which component, and which journey led to each conversion. In a review you can point to the exact content that

One platform for every brand your team manages

Spectare is built for teams running more than one website. Each brand gets its own workspace with separate content atoms, users, and billing

How atoms reach the visitor

An atom is a focused piece of content with a single job: explain one feature or answer one question. Each atom carries metadata about which

Works on whatever stack your client already runs

WordPress, Next.js, or a plain script tag: Spectare drops into the client's existing site without a rebuild or a migration. It sits alongsid

What is Spectare

Most websites show every visitor the same page. A first-time visitor curious about your product sees the same thing as a buyer who has alrea

Analytics shows live serving counters alongside performance data

The Spectare analytics API response includes live serving counters that reflect how often each atom and component combination is actively be

Warm one audience, not the grid

The Spectare cache warm endpoint now accepts an audience parameter. Pass a single segment name or an array of names and the warmer builds on

Email and password sign-in

Getting started with Spectare no longer requires a Google or GitHub account. You can now create an account and sign in using any email addre