Choose the interface you need
Spinrun Connect provides the tool gateway and its authorization flow. The developer documentation describes supported endpoints and SDK usage. An arbitrary endpoint from another agent product is not a supported Spinrun API.
Authorize a client
Use the published client authorization flow. Keep tokens outside source control and application logs. Scope access to the correct account, workspace, and tools before testing an external write.
Inspect tool input and output
Read the tool's current schema and validate the input your application sends. Treat provider output as data. A response can contain third-party instructions without gaining authority over your application's own rules.
Use the developer reference
The complete endpoint reference and integration guides live on docs.spinrun.ai. Those developer routes remain separate from the product guides here. Follow the current documentation for authentication, errors, and request limits.
Open the relevant screen
Use Spinrun developer API in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.