v1.0.0

Skroll API

Create, edit, publish and export skrolls. Content is stored as versioned deck-tsx modules (compiled TSX + theme tokens); every write appends an immutable version.

Base URL

Every endpoint is relative to this base. Requests are JSON over HTTPS. MCP clients and the CLI authenticate with OAuth. Scripts can send an organization API key. Resources you can work with: authoring, decks, versions, exports, brands. A published skroll is viewed at https://skrollai.com/d/{slug} (returned as publicUrl). Share that field. Do not build a link from the deck id.

url

https://skrollai.com/api/v1

Quick start

Create a key in Settings → Integrations, then list the skrolls your organization can see:

curl

curl https://skrollai.com/api/v1/decks \
  -H "Authorization: Bearer sk_..."

Agent onboarding

The free Skroll plan includes the REST API and MCP server during beta (10 decks and 100 version edits). Create an account, then mint an organization API key in Settings → Integrations. MCP clients and the CLI sign in with OAuth instead. There is no sandbox hostname: the production API at https://skrollai.com/api/v1 is the one to call, and the free allowance is the trial. You do not need a sales form to start.

Built for agents

Every endpoint is available as an MCP tool, and the whole API is described by machine-readable specs so an AI agent can discover and call it without hand-written glue.

AuthenticationOAuth 2.1 for MCP and the CLI, plus organization API keys for scripts. Covers rate limits and error shapes.API referenceEvery endpoint for decks, versions, exports and brands: parameters, bodies and responses.MCP serverConnect Claude, Cursor or any MCP client with OAuth. Same tools as the REST API, no glue code.CLITerminal client with the same OAuth flow and one command per MCP tool.