AI agents for Sanity
A Monmo agent works with Sanity the way a developer who also cares about the content would. It answers questions about your content with GROQ, drafts documents editors can finish in the Studio, changes schema types through pull requests and tests content migrations on a staging dataset before production. It uses the API token you connect, and asks before it creates, publishes, migrates or deletes anything.
Updated 2026-11-13 · Free to start. Paid plans from $15 a month.
What agents do in Sanity
Answer content questions with GROQ
Ask which posts still mention the old pricing or reference a retired product, and the agent writes the GROQ query, runs it against your dataset and lists the documents with links into the Studio.
AskWhich published posts mention the Starter plan or reference the retired Classic product? Link each one.
Draft documents for editors
From a brief or Google Docs, it creates a draft document of the right type, with Portable Text body, references and an image chosen from your assets. Editors finish it in the Studio.
AskDraft a post document from this Google Doc, with the author and category references set. Leave it as a draft.
Change a schema through a pull request
To add a field, such as an SEO description on post, it edits the schema type in your Studio code, adds validation and opens a GitHub pull request. Merging and deploying the Studio ask first.
AskAdd a required SEO description field, 160 characters at most, to the post schema and open a pull request.
Test a content migration
When a field is renamed or reshaped, it writes the migration, runs it against a staging dataset, counts the documents changed and shows samples. Running it on production waits for your approval.
AskWrite a migration that moves author names into author references. Test it on the staging dataset first.
Translate documents
Following the way your Studio handles languages, by field or by document, it drafts the Japanese version of each document, keeping references and product names intact, for an editor to review.
AskDraft Japanese versions of the ten newest posts the way our Studio stores translations. Leave them for review.
Find broken references and gaps
Each month it runs GROQ checks for references to deleted documents, images with no alt text, slugs that clash and required fields left empty in older documents, and drafts the list of fixes for Slack.
AskEvery month, check for broken references, missing alt text and duplicate slugs, and list what needs fixing.
Prepare a launch release
For a launch it gathers the documents involved, checks each one is complete and prepares them to publish together at the agreed time. The publish itself happens only once you approve it.
AskGather every document for Thursday's launch, check they are complete and get them ready to publish together.
How it connects
- 1You create an API token for the project in Sanity's manage page and connect it once. A Viewer token covers questions and audits; an Editor token is needed for drafts and migrations.
- 2Sanity suits a web developer agent, which also needs GitHub for schema changes, and a content agent that drafts and translates. Give each the token that fits its work.
- 3Running GROQ queries and reading documents and schemas needs no approval. Creating or editing documents, publishing, running a migration, merging a schema change and deleting anything each ask first.
Questions people ask
Can an AI agent write GROQ queries for Sanity?
Yes. Describe what you want to find in plain words and a Monmo agent writes the GROQ, runs it against the dataset you choose and gives you the results with the query, so a developer can reuse it in the front end. Reading needs no approval.
Can it change our Sanity schema?
It changes the schema in code and you approve the merge. Because Sanity schemas live in your Studio's code, the AI agent edits the schema types, adds validation and opens a pull request in GitHub. Deploying the updated Studio asks first, and existing content is migrated separately.
Will it publish documents in Sanity without asking?
No. It creates drafts, which editors see in the Studio, and publishing asks first. Publishing in Sanity often triggers a rebuild on Vercel or another host, so the card lists the documents and what will change on the site. It works through the Sanity connection, or in its own browser when the connection does not cover something.
Can it run a content migration safely?
It tests first. The agent writes the migration, runs it against a staging dataset or a copy, counts the documents changed and shows you samples. Only then does it ask to run it on production. If a dataset copy is not available, it can run the migration in small batches you approve one by one.