Join the Sanity Challenge: $2,500 in prizes for FIVE winners!

Path one: Ship an agent that queries real content

Build an agent, then point it at a Sanity Context MCP endpoint backed by a Knowledge Base. Any agent framework, hosted anywhere.

Build anything that needs an answer it can't afford to get wrong. A board game companion that knows the errata contradicts the rulebook. A better interface to your favorite open-source docs. A eurorack planner that knows what actually fits in your case. An award-travel agent that untangles which transfer partner story is current. A car repair agent? A camera gear-head compendium? The sky is the limit.

Point Sanity Context at a website, a set of files, or your own Sanity content, and it distills a navigable Knowledge Base your agent reads through MCP. Every entry stays linked to the source it came from. When two sources contradict each other, both claims surface side by side with their sources, and the decision you make carries across future builds. It all lives in your Sanity Dashboard.

The strongest submissions will show an agent that only works because the content was structured. If a keyword search would have gotten you the same answer, aim higher.
 

Note: Knowledge Bases are in beta and currently index up to 150 documents. Design for that budget, or point your agent at your full dataset through a Context MCP endpoint with embeddings enabled. Both count for Path One.

Path two: Vibe-code something strange

Prompt your way to a working app. Any AI-native IDE, Next.js or Astro on the front, Sanity behind it.

This one is judged on the build as much as the result. How deep did you get into Sanity's features? Did you customize the interface? Build a new component to turn videos into gifs? Create a workflow that kicks off an external API call? A rough app with an honest writeup beats a polished one with three sentences.

Bonus points for reaching past the Studio. Two things we'd especially like to see prompted into existence:

• App SDK: build a custom app on top of your content, with real-time data and your own interface, instead of another read-only frontend.
• Workflows: model a process (content reviews, translations, and so on) as data next to the content, so an agent can move a draft forward and a person can approve it through the same transitions.

Neither is required. A submission that uses one well will stand out from a pile of blog templates.

How To Participate

Publish a post on DEV using the prompt submission templates above and be sure to include the required challenge tag: #sanitychallenge. You may submit to both paths, but you must create a separate post for each.

If your app requires logging in, please provide testing credentials in your submission and/or instructions on how to best test your application for judges.

Optional but encouraged: embed your agent session. Upload a transcript from Claude Code, Gemini CLI, Codex, GitHub Copilot CLI, or Pi, curate or slice the parts worth showing, and drop it straight into your post. It beats a screenshot, and for Path two it's the most direct way to show your work.

Share, Embed, and Curate Agent Sessions on DEV [Beta]

Jonathan Gottfried

Jonathan Gottfried

Jonathan Gottfried

Follow

for The DEV Team

Mar 4

Share, Embed, and Curate Agent Sessions on DEV [Beta]

#ai #forem #devto #gemini

76 reactions

20 comments

3 min read

Head to the Agent Sessions uploader to get started. Two things to remember: uploads are unlisted by default, so use the Make Public button or judges won't be able to open your session. And check your transcript for keys and sensitive data before publishing. There's a redaction layer, but it won't catch every edge case.

Please review our judging criteria, rules, guidelines, and FAQ page before submitting so you understand our participation guidelines and official contest rules such as eligibility requirements.