Join hundreds of creators who automate their launches with Tokei
Your agent handles your marketing while you stay in control.
How it works
Launch your first automated workflow
Three real exchanges — building a page, reading stats, and wiring automation — run entirely from an agent or the terminal.
Example output — the numbers are illustrative; the commands and field names are real.
Create or edit a launch page from chat
The agent clones a proven starter, then reshapes it. pages:updatePATCHes copy, dates and reward tiers — iterating until it's right.
Monitor campaign stats from chat
Ask in plain language; the agent runs read commands and summarizes. A read-only key covers everything — stats, leaderboard and entries:list.
Wire up a webhook for real-time events
Subscribe to entry.created. The whsec_ signing secret is shown once; deliveries are HMAC-signed and retried on failure.
Works with your agent
Drop it into any MCP client
One command to connect
Register the MCP server and Claude Code can call all 17 operations as tools — no wrapper code.
$claude mcp add tokei --env TOKEI_API_KEY=tokei_k_... -- npx -y tokei-agent mcpA SKILL.md agent reference ships inside the npm package — all 17 commands with worked examples.
Skill-native, or just shell out
The bundled SKILL.md carries OpenClaw-compatible frontmatter, so the agent picks it up as a first-class skill.
Prefer no MCP at all? Any agent that can run a shell can call npx tokei-agent <command> directly — every command prints JSON to stdout.
Agent-safe keys
Let your AI safely access Tokei
Giving an autonomous agent access to your account should feel safe by default. Tokei API keys are built for exactly that.
Read-only by default
The key-creation UI defaults to read-only scope. Write access is opt-in, so an agent can only change things when you deliberately hand it a write key.
Keys that expire
Set an expiry of 1, 7, 30, 90, or 365 days — 90 days by default. Hand an agent a one-day key and a leaked credential can't linger.
Security email on webhook create
Whenever a webhook is created via the API, you get a security email — so a new outbound integration can never be set up silently.
Rate limits agents can read
Every authenticated response carries X-RateLimit-* headers, so a well-behaved agent self-throttles instead of hammering the API.
Human in the loop
The agent drafts and operates. You approve.
Nothing that reaches the public happens on its own. Page changes going live, emails, winner picks — each one waits for a human to approve it. The agent does the legwork: cloning, editing drafts, pulling stats, and preparing changes for your sign-off.
This is a product principle, not a limitation — it's how you move fast without shipping something you didn't mean to.
For agents & developers
Point your agent at the docs
Agents discover Tokei through /llms.txt — the index that links the API reference, the OpenAPI spec, and the tokei-agent tooling.