网页 综合 更新时间 2026-09-18 13:00:00

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

自动蜘蛛 dev.to 正文约 6000 字
Join the Sanity Challenge: $2,500 in prizes for FIVE winners! - DEV Community
Posted on Sep 18 • Edited on Oct 22 • AI-assisted
Showcases creative AI agents and candid build logs
We're excited to announce our newest challenge with Sanity!
The Sanity Challenge runs September 18 to October 4. Build an AI agent on structured content, or vibe-code an app with Sanity behind it. $2,500 in prizes.
New to Sanity? Sanity is the AI Content Operating System. Your content lives in the Content Lake as JSON documents, with schemas you define in TypeScript and query with GROQ. You can use Sanity to build anything that you can imagine with structured content as your starting point.
Read on to learn more.
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.
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:
Neither is required. A submission that uses one well will stand out from a pile of blog templates.
Every submission, both paths, needs to include your Sanity project ID or a link to a public dataset URL.
This lets the Sanity team look at how you actually modeled and used your structured content, which is a real part of judging. There's a section for it in both templates above. Submissions without it may be considered incomplete, so don't skip it.
Path one: Ship an agent that queries real content submissions will be evaluated for:
Path two: Vibe-code something strange submissions will be evaluated for:
Three winners from Path one, "Ship an agent that queries real content," will receive:
Two winners from Path two, "Vibe-code something strange," will receive:
All participants with a valid submission will receive a completion badge on their DEV profile.
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.
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.
We can't wait to see what you build. Questions about the challenge? Drop them in the comments below.
Good luck and happy coding!
Just when I thought I was out, they pull me back in.
That's what she said!
I think you are the best
I'm going to participate in this, no matter what!! I'm so excited!!!
Heads-up for the judges: my GitHub account was suspended on 20 Oct (unrelated to the challenge, appeal pending), so the repo for my Path One entry, Clockwrit, moved to GitLab with its full history: gitlab.com/RaYYeR220/clockwrit. The submitted state is commit f474794; the post, live app, video and Sanity project are unchanged apart from the updated repo link. Post: dev.to/rayyer/clockwrit-every-hour...
Entered both paths, on one shared dataset: an Oracle → Azure migration knowledge graph with 446 documents, where every claim points at a source.
Path One: Keyword search found the facts but lost the sources. An agent over two Sanity Context endpoints, with a blind four-way eval. Keyword search got 14 of 18 verdicts right but cited the required publishers only 4 times out of 16. The GROQ agent cited them 12 times and grounded all 18 answers.
Path Two: The Legacy Obituaries. Every Oracle feature that didn't survive the move to Azure gets a newspaper obituary: born in, cause of departure, survived by. An App SDK desk certifies the notices, and a Workflows lifecycle runs over the queue.
Both posts include the agent sessions and what went wrong along the way. Thanks for running this one, an
访问原文 返回搜索 https://dev.to/devteam/join-the-sanity-challenge-2500-in-prizes-for-five-winners-514m
本页为82搜索生成的网页快照,内容来自站内索引;演示数据的原文链接仅作示例。