Skip to content

About

Starters for building AI agents on eve, each pointed at something real in San Antonio. Answer the five Before you build questions first, then fork one. A DEVSA project.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

Repository files navigation

agent-patterns

Starters for building AI agents on eve, the open-source agent framework, each built on one of Vercel's eve templates and pointed at something real in San Antonio.

They're here to learn from. Each one is a pattern you'll find in most organizations, wired to a DEVSA example so you can watch it work, with a section on what to change to point it at your own.

Start with Before you build. It's five questions: one workflow, who owns it, what information it needs, where a person signs off, and the one number that tells you whether it worked. Every starter opens with its own answers. Do yours before you fork one.

The starters

Starter The pattern Built on Status
Ask your data Answer questions from data you'd bet on, with the source, so every answer can be checked eve Agent with Python Ready
Draft, approve, act Draft in a house voice, wait for a person to approve, then publish eve Content Agent Ready
Weekly recap and triage Read what came in this week, sort it, and send one digest someone actually reads eve GitHub Maintainer Next
Fill the form Answer a grant application, RFP or questionnaire from answers you've already approved, inside each question's limit, with a person signing off on every answer eve, borrowing from AutoRFP and the approved-answer-library idea in rfp-autopilot Later

What you need

Node.js 24, pnpm, and a free Vercel account. Ask your data also needs uv for its Python backend. Each agent calls its model through Vercel AI Gateway, which charges for the model at the provider's price; trying a starter out costs cents, and each README says what it calls.

eve is a 1.0 release candidate, and its API can still change between releases. Each starter pins the eve version it was built and tested with.

How each starter is built

Each folder starts as a copy of one Vercel template at a named commit, with its license kept. DEVSA's changes go on top and are listed at the end of the folder's README, so you can see exactly what's the template and what's ours, and pull in the template's own fixes.

Contributing

Built one of these for your own industry? Show it in #build-and-tell on Discord, or open an issue. Found a bug in eve itself? eve asks for an issue on vercel/eve before any pull request.

Credit

Each starter is built on a Vercel template and keeps that template's license. eve is © Vercel, Apache-2.0. This is a DEVSA project: built with eve, not by or with Vercel.

About

Starters for building AI agents on eve, each pointed at something real in San Antonio. Answer the five Before you build questions first, then fork one. A DEVSA project.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Contributors

Languages