The product

Everything around the model.

Six pieces that turn a capable model into an agent that builds your way. Every card below is running. Open one up.

Start free Drive a session

Up-to-date setup

A catalog of kits

No more agents installing last year's API from memory.

serviceStripepayments2026-11-03

modelClaude APIllm2026-11-03

frameworkNext.jsfrontend2026-11-03

librarypgvectordatabase2026-11-03

toolPlaywrighttesting2026-11-03

Connect once

One MCP server for every agent

One connection for every agent your team uses.

search_catalogget_kitget_pathlist_projectsget_projectget_stepcreate_projectadd_kitscomplete_stepreopen_step

From clone to production

Designed paths

The agent always knows what's next and what done means.

saas-starter · 4 of 8 · next: first-page

No reinventing

Good patterns by default

Code that looks like your senior engineer wrote it.

Stripe kit

event = await request.json()

event = stripe.Webhook.construct_event(body, sig, secret)

Verify the signature against the raw bytes before parsing

Pick up where it stopped

Progress that carries over

Nobody re-explains what yesterday's session already did.

uv run alembic check reports no differences

uv run pytest passes, including a test for the new routes

complete_step first-model

Shared and permissioned

Built for teams

Every agent call on the record, for the people who answer for it.

agent:callcomplete_step billingCI agent

agent:callsearch_catalog paymentsDana · Claude Code

agent:callcomplete_step first-pageSam · Cursor

The catalog

Search it like your agent does

31 kits, each with install steps, environment variables, the patterns to follow and the mistakes to avoid. This is what lands in your agent's context when it calls get_kit.

search_catalog31 kits

servicepayments reviewed against its docs 2026-11-03

Stripe

Payments and subscriptions: Checkout, the customer portal, webhooks and invoicing.

Install

uvuv add stripe

npmnpm install stripe

clibrew install stripe/stripe-cli/stripe

Environment

STRIPE_SECRET_KEY secretsk_test_... in development, sk_live_... in production
STRIPE_PUBLISHABLE_KEYpk_..., safe in the browser
STRIPE_WEBHOOK_SECRET secretwhsec_..., verifies that webhook calls came from Stripe

Patterns to follow

Your database is the source of truth for plans and entitlements; Stripe mirrors prices and takes payment

Hosted Checkout and the customer portal instead of building card forms

Webhooks for every subscription change, verified with the signing secret and handled idempotently

Gate features on entitlements resolved from the plan, never on a Stripe price id scattered in code

Record a finished checkout when the buyer returns too, so access doesn't wait on the webhook

Avoid

Trusting the success redirect alone: renewals, cancellations and failed payments only arrive as webhooks

Parsing the webhook body as JSON before verifying its signature against the raw bytes

Using live keys in development, or test keys in production

Try it

Drive a session. Hand it off.

Pick a build and an agent, run the path a step at a time, then switch agents half way and watch the new one pick up from the last one's notes.

Build

Agent

claude code · ~/invoicergyve connected

Press “Run next step” to start a session.

0/9

InvoicerSaaS on FastAPI + Next.js

Clone and name the product
Make your own secrets
Run the stack
Add your first domain model
Build its pages
Turn on billing
Prove it in a browser
Deploy
Watch it in production

Tool calls: 0
Checks passed: 0
Sessions: 0

Autopilot is driving, handing the project to a new agent every few steps. Press any control to drive it yourself.

Your next agent session starts briefed.

Start a project on a path, connect your agent with one command, and watch it build on patterns that hold up.

claude mcp add --transport http gyve https://api.gyve.dev/v1/mcp

Start free, no card hello@gyve.dev