Start Here
Customer Integration
The customer path is hosted: subscribe at sweetpotato.dev, provision an application, save the
one-time scoped secret, install an authorized client, then integrate https://api.sweetpotato.dev.
SPAPS has no free tier or trial. It is pre-1.0, so contracts may still change.
Local runtime, source checkout, FastAPI service, deployment, and release paths below are for authorized maintainers—not customer onboarding.
Use this page when you know your role but not the first SPAPS doc to open. Each path ends with a concrete proof signal before you move deeper into implementation.
This site was source-checked at Sweet Potato
5b09d3df1194577c5313c865fef1db98f694cdea. Read Source truth and
verification before relying on a route, package version, or release claim.
Solutions Consultant
| Step | Open | Proof |
|---|---|---|
| Run the workshop path | /solutions/field-kit | npx spaps quickstart --json, npx spaps verify --json, and npx spaps tools --json are captured |
| Explain the product boundary | /overview/what-is-spaps | The room understands SPAPS as app-level identity, billing, and entitlement control, not enterprise IAM |
| Prepare the leave-behind | /solutions/field-kit#leave-behind-artifacts | App slug, auth mode, revenue trigger, entitlement, verification result, and next skill are named |
App Integrator
| Step | Open | Proof |
|---|---|---|
| Pick the package surface | /packages | CLI, TypeScript SDK, Python client, quickstart package, or companion package is selected |
| Start local runtime | /packages/spaps-cli | npx spaps local, npx spaps quickstart --json, and npx spaps verify --json produce mode-aware output |
| Check key and origin rules | /guides/api-keys-and-origins | Publishable keys stay browser-scoped and allowed origins are explicit |
Backend Maintainer
| Step | Open | Proof |
|---|---|---|
| Boot the Python stack | /tutorials/local-development | make local-proof-up and curl http://localhost:3301/health prove the active Python server path |
| Trace the request shape | /overview/request-lifecycle | Middleware, dependencies, routers, services, and repositories are in the expected order |
| Run the canonical test path | /guides/testing-and-tdd | make pytest is used instead of raw pytest |
Scenario Proof
Before changing first-run docs, validate the role paths from this repo:
npm run first-run:dry-run
npm run first-run:live -- --jsonWhen a scenario command fails, route it through Troubleshooting symptom decisions before changing the field-kit or backend-maintainer path.