Implement content experiences
Connect
SPIRITT
Agility CMSAgility CMS
Make structured content work everywhere
Build content-driven apps and editorial operations from Agility CMS models, pages, and localized records. Give SPIRITT the outcome and put your connected account to work.
What you can do with Agility CMS.
Build from the real model
Read content models, page modules, sitemaps, and linked content before implementing the experience.
Keep experiences current
Synchronize page and content reads into an external app with recoverable sync state.
Give editors precise work
Turn missing routes, locale gaps, and inconsistent content into source-linked correction tasks.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your Agility CMS workflows, connected apps, and finished outcomes.
02
Connect Agility CMS
Connect Agility CMS and select the account and records your agent should work with.
03
Hand over a mission
Describe the result, scope, and handoffs. SPIRITT builds the workflow and follows the work through.
Hand over a mission.
Choose a mission. Make it yours.
Put Agility CMS to work.
Make structured content work everywhere
Questions
Agility CMS, with SPIRITT.
01What can SPIRITT do with Agility CMS?+
Build content-driven apps and editorial operations from Agility CMS models, pages, and localized records. Read content models, page modules, sitemaps, and linked content before implementing the experience. Synchronize page and content reads into an external app with recoverable sync state.
02Can SPIRITT build an app around Agility CMS?+
Yes. Ask it to "build a structured content app". Read our Agility CMS models, page modules, sitemap, and selected content to build the requested content-driven app. Preserve instance, locale, channel, and fetch context, deploy through the connected hosting project, and verify rendered routes against the source page records.
03How does SPIRITT separate preview from published content?+
It uses the specified instance, API type, locale, and channel for every content query. Preview data stays behind the intended access boundary, and sync tokens are tracked per source context so preview and published records are not silently mixed.
04How does Agility CMS work with my other apps?+
Connect the apps your mission uses. GitHub to implement content experiences; Vercel to deliver content apps; Linear to own editorial corrections. SPIRITT carries the handoff through and checks the result in the destination.
05What should I know about the Agility CMS connection?+
Agility CMS supports content, model, page, sitemap, and incremental sync reads. Sync Pages retrieves page data; it does not publish or deploy the CMS. External app delivery uses a separate connected hosting workflow and explicit fetch or preview context.
06How do I get started with Agility CMS?+
Open a SPIRITT workspace, connect Agility CMS, and name the target records and desired outcome. Start with "Build a structured content app" or bring your own mission. Set the scope for changes and external actions, then let your agent run the work.