Documentation.
Guides, API reference, SDKs, recipes, and a glossary of everything we name. Spot something off in the docs? Email hello@wrxstack.com.
Three ways to start.
Pick the path that matches how you work. Each one ships a real outcome by the end.
Install in five minutes.
Create an account, invite a teammate, call the API from your repo, ship a workflow.
Open guide →Your first assistant.
Define a workflow, give the assistant scoped tools, watch it run a full ticket end to end.
Open guide →Hello, API.
Authenticate, list assistants, create a task, ship the first webhook handler.
Open reference →The full map.
Six sections. Each owned by the team that ships the underlying system.
Guides
Conceptual walkthroughs, written conversationally. Read these to understand how everything fits.
API reference
Every endpoint, every parameter, every error, plus webhooks and the MCP server. With curl, Python, and TypeScript samples for each.
SDKs
Planned clients for Python, TypeScript, Go, and a CLI. Call the REST API directly today, or request early SDK access.
Recipes
End-to-end examples you can copy. Real workflows from real teams running on the platform.
Reference
Configuration keys, audit log schema, hard limits, the canonical changelog.
Glossary
Every term we use, defined in two or three sentences. Bookmarked by every new hire in their first week.
Most-read this week.
What new builders open first. Sorted by traffic.
SSO with Okta
SAML 2.0, attribute mapping, JIT provisioning, fallback procedure.
Webhooks & signatures
Subscribe, verify, retry. Idempotency. Replay from the audit log.
Import from Notion
Map databases to the work graph. Preserve permissions. Backfill history.
Tool calling
Expose actions to the assistant. Scope them. Audit every call.
Auto-redline contracts
Wire the assistant to your playbook. Flag risky clauses. Route to legal.
MCP server
Connect wrxstack to any MCP client. Tools, resources, and scoped access over the Model Context Protocol.
Every page.
The full A-to-Z. If a link belongs in another section, file an issue.
Stuck? Email support.
Or hop into Slack.
Email me and I'll reply as soon as I can, usually the same day. The community Slack is the fastest path for "how do I…" questions.