Sign-in, tokens, credits, limits and what to do when a connection fails. For setup, start with the overview.
Signing in
How does sign-in work?
Your app registers itself with Spritory and opens a sign-in page in your browser. You sign in, and a consent screen shows the app's name and where it will return to. Approve, and the app can use Spritory. You do not copy anything.
Sign-in needs an app that supports OAuth for MCP with dynamic client registration. Claude, Claude Code, Codex, Cursor, VS Code, Gemini CLI and OpenCode all do.
Personal tokens
Use a personal token when your app cannot sign in, or in scripts and CI.
- Open your Agents page and find Personal tokens.
- Name the token and click Create token. Copy it right away, because it is shown only once.
- Add the server URL and this header to your app:
URL: https://spritory.com/api/mcp
Authorization: Bearer spt_your_tokenA token acts as your account. Do not commit it to a repository or paste it into shared chats. If one leaks, revoke it on your Agents page and create a new one.
Managing connected apps and tokens
Your Agents page lists every connected app and every personal token. Revoke any of them there. Revoking takes effect immediately, and the app must sign in again to get back in.
What can an agent do with access?
It can work with your sprites, effects and art styles, and export them. It cannot change your account, your email or your billing.
Credits and limits
How credits work
Each operation costs 1 credit. Renders and exports cost 1 credit per 4 frames, at least 1. Each call adds 1 more credit. A finished sprite usually takes 10 to 20 credits, and a finished effect 20 to 40. Working in the editor yourself never uses credits.
Your remaining balance is on your Agents page. See the tools reference for the full breakdown.
Rate limits
Your account can make 60 calls per minute. If your agent reaches the limit, it is told to wait a minute. Asking for work in larger batches helps.
Script limits
One script can call up to 200 operations and return up to 8 images. A bigger job continues in the next call.
Your library
Exports expire, your saves do not
Files your agent exports are download links that expire after 7 days. Your saves stay in your library, so you can export them again at any time.
Edits from several places
If a save changes while your agent is editing it, the agent reads the latest version and applies its change again, so it does not overwrite your work. The editor does not check this yet, so keep one editor tab open per asset.
Saves keep no history
An edit replaces the previous version. Before a big rebuild, ask your agent to duplicate the save first.
Troubleshooting
- The sign-in page does not open. Your app may not support OAuth for MCP. Use a personal token instead.
- The consent page says a license is required. Agent access is part of full access. Check the account you signed in with, or see pricing.
- Unauthorized. The app's access was revoked, or the token is wrong or missing. Sign in again from your app. With a token, check that the header reads
Authorization: Bearerfollowed by a space and the full token. - Tools do not appear. Restart your app after changing its config, and check that the URL ends in
/api/mcp. - Out of credits. Your agent is told when credits run out. Nothing you have made is affected, and the editor keeps working.