Build
Pick a result. Build it end to end.
You write the agent. These four guides show what serving it looks like: auth, isolation between users, human approval, and a deploy. Each starts in an empty folder, shows real requests and responses, and says what was run and what was not. For how things work underneath, the docs go deeper.
A build guide is one end-to-end path to a working result, not a feature tour. It lists the time it takes, the skill level and the exact package versions it was written against, so you can tell whether it still matches your setup. Commands and code are in order and every step ends in something you can check. Choose by outcome first: read the "You end up with" list on a card and pick the guide whose result you need. Then use the time and level to decide whether to start now. If a term is unfamiliar, the Get started tutorial covers the basics.
- Build a production-grade ReAct agent in PythonA support agent that looks up and refunds orders, served as an API with JWT auth, per-user rate limits, Postgres memory, tests and Docker files.
- A ReAct agent with two tools that check who is asking
- A refund tool that moves money once, even when asked twice
- A REST API with JWT auth and per-user rate limits
- Threads stored in Postgres with a Redis cache
- Tests that run without a model API key
- A Dockerfile and docker-compose.yml with Postgres and Redis
- Serve a support agent to many customers without leaking dataServe one support agent to two companies with JWT auth. Show with real requests that users cannot read each other's threads or memories, with Postgres and a rate limit.
- A JWT-protected support agent that serves users from two companies
- Proof, with real requests, that one user gets 404 on another user's thread
- Long-term memories that each user can only search and list for themselves
- Threads that survive a restart, stored in Postgres through the checkpointer
- A per-user rate limit that answers 429 with a retry time
- Let an agent propose refunds that a human approvesPut a refund tool behind interrupt(), approve it over the API with an interrupt id, and keep a crash or a double click from refunding twice.
- A refund tool that pauses for approval and validates the answer against a schema
- An approval over REST that names the exact interrupt it answers
- A tool ledger that stops a re-run of the same step from posting or refunding twice
- A 409 when two requests hit one thread, and for an answer that is stale or misdirected
- Ship an agent to Kubernetes with the files 10xgraph generatesGenerate the Dockerfile, Compose file and Kubernetes manifest with 10xgraph build, add Postgres, Redis and secrets, and see what the probes and shutdown settings do.
- A Dockerfile that runs Gunicorn as a non-root user, built and started for real
- A Kubernetes Deployment and Service with readiness, liveness and graceful shutdown set
- Postgres and Redis wired in, with every secret coming from a Kubernetes Secret
- A clear list of what was checked locally and what needs your cluster