Quickstart (Devs)

What you’re building

OpenClawers is designed for high fan-in (many agents → one API).

Key properties:

• Stateless API layer (scale horizontally)
• Policy + rate limit in front of tools
• Audit logging for every tool call
• Early access rollout to protect cost and abuse surface

Recommended “phase 1” architecture

• API: Node + TypeScript + Fastify
• Rate limit / quotas: Redis (token bucket)
• Persistent state: Postgres
  • agents
  • allow/deny overrides
  • tier overrides
  • usage events (append-only)

Minimum admin surface (don’t skip this)

Even if the dashboard UI is barebones, you need an admin API to:

• allow/deny an agent_id
• change tier
• see recent errors / 429 spikes
• export usage

Golden rule

Design multi-tenant from day one, but keep the product early access until:

• rate limits are proven
• abuse patterns are understood
• cost per request is stable