RUTY / DEVELOPERS

Your key. Your workspace.

Create and manage keys in the console. Existing ReelMind and Yiha keys continue to work through Ruty; the key format remains unchanged.

terminal

export RUTY_API_KEY="YOUR_API_KEY"

curl https://ruty.ai/v1/models \
  -H "Authorization: Bearer $RUTY_API_KEY"

Account sessions and API keys

The console uses your signed-in account to manage keys and view usage. REST generation, MCP and CLI use API keys. The server verifies identity and task ownership on every protected operation.

Keep credentials on your server

Use environment variables. Never commit API keys, put them in URLs, or ship them in browser JavaScript. Revoke a compromised key in the console and create a replacement.

Team context

The CLI accepts RUTY_TEAM_WORKSPACE_ID and optional RUTY_TEAM_PROJECT_ID. These must be valid UUIDs. The gateway preserves the existing ReelMind team context headers and the backend checks your access.