Documentation.
The documentation for Atlas lives inside Atlas, next to the product it describes, so it always matches what ships. Start here to find the right page for the REST API, webhooks, the MCP server, and connectors.
Where to find it.
Each link opens the current page in the Atlas documentation.
Getting started
What Atlas is, how a workspace is organized, and where each module fits.
Open →REST API
The public API for tasks, projects, webhooks, and personal access tokens, with an OpenAPI 3.1 spec.
Open →API reference
Every endpoint, its parameters, and its responses, generated from the spec.
Open →Authentication
Personal access tokens and OAuth, scopes, and how to send the bearer token.
Open →Webhooks
Events, payloads and headers, signature checks, and delivery retries.
Open →MCP server
Connect AI agents to Atlas through the Model Context Protocol, and browse the tool catalog.
Open →Connectors
Setup guides for the connectors Atlas lists, including Gmail, Google Calendar, and Google Drive, which are available now.
Open →Glossary
The terms Atlas uses, defined in one place.
Open →Changelog
What changed in Atlas, release by release.
Open →The three things you need.
Enough to make a first call. The API overview covers the rest.
- Base URL
- https://api-atlas.wrxstack.com/v1
- OpenAPI spec
- api-atlas.wrxstack.com/v1/openapi.json
- Authentication
- Authorization: Bearer <token>
Help for Folio.
Folio, which turns your resume into a personal website, has its own help center for building, publishing, and sharing your portfolio.
About the docs.
Why is the documentation on atlas.wrxstack.com?
So it changes in the same place, and at the same time, as the product. A copy on this site would drift out of date, and an earlier version here did. Keeping one source means what you read is what Atlas does.
Which language can I call the API from?
Any language that can make HTTPS requests. The API is plain REST with JSON, and the OpenAPI 3.1 spec works with standard code generators if you want a typed client.
I found a mistake in the docs. Where do I report it?
Email contact@wrxstack.com with the page link and what looks wrong.