Get started
Introduction to Snugnut
Snugnut provides services for apps and agents that need shared data, background
work, virtual economies, or simulations. Choose the services your project needs
and use them through one HTTP API or the snug command line.
- Services
- 70+
- Endpoints
- 1,200
- Ways to call
- HTTP + CLI
Start with what you’re building
You don’t need to learn the whole catalog. Pick a capability your project needs, try its example, and open the guide when you’re ready to use it.
World simulation
Manage entity state, simulate populations, and control the pace of a simulation.
Worker coordination
Assign exclusive access to resources, request human approval, and track agent budgets.
Virtual economies
Track credits, reserve inventory, and settle an exchange only when both sides are ready.
Interactive stories
Store story state, respond to player choices, and simulate how information spreads.
The full catalog also covers storage, messaging, identity, game mechanics, forms, onboarding tours, and waiting rooms.
Familiar pieces in one interface
We call it soft infrastructure: services you can reach through a shared API, without a separate vendor account, console, or capacity plan for every capability. You choose the services and keep control of your app’s rules.
One envelope for success and failure, with a machine-readable error code.
Tokens and scoped API keys, with organizations, SSO, and directory provisioning.
A shared grammar for filtering, sorting, and pagination.
Response headers show the available rate-limit budget.
Use it from your code, terminal, or agent
Call the HTTP API from your own code, use the matching snug command line, or give
an agent the OpenAPI description. All three use the same services. You don’t need a generated client.
Each API endpoint has a matching CLI command. Use --output json when a script
or agent needs to read the result.
snug --output json kv get user/preferencesUse ordinary HTTP requests and JSON. The API reference describes each request, response, and error, with a Try It panel for making calls.
GET /api/v1/kv/user/preferences
Authorization: Bearer <token>Find the OpenAPI schemas
On your API server, use these paths:
| What you need | Path |
|---|---|
| Every service in one schema | /openapi.json |
| One service’s schema | /openapi/{service}.json |
| Swagger UI | /docs |
These are API-server paths. This documentation site has its own API reference.
Make your first call
Follow the quickstart to connect, sign in, and store a value. Then explore the services you want to use.