Skip to main content
Use the Straddle Wizard to prepare an application for integration work and run the Straddle skills in your coding agent. It detects project context, helps load the plugin, and records where the work stands. For the complete path from setup to sandbox results, follow Build your first integration.

Check project readiness

Use Node.js 22.18 or later. Open the repository that will call Straddle, then start the focused setup workflow:
1

Confirm the project context

Check the detected language, framework, installed Straddle SDK, and existing payment provider. Correct the detected values when needed.Choose the payment operations, integration type, SDK, and notification path. Unresolved choices stay visible for the agent to discuss with you.
2

Choose your agent

Select Claude Code, Codex, or Cursor. In Auto mode, the Wizard starts the signed-in command-line client in your terminal. In Manual mode, it gives you the message and setup steps for your own agent session.The Wizard offers the plugin installation or update needed by the selected client. Cursor installation uses the steps shown in the client. See Install the Straddle plugin for each client’s setup.
3

Read the setup report

The Setup skill writes straddle-setup.md at the repository root. Read its checks for the CLI, API key presence, environment, integration type, acting account, SDK, and MCP connections.Resolve any blocking finding, then run the setup command again to check the result. Setup records what is ready and what needs work in that report.

Check configuration before requests

Set STRADDLE_API_KEY in the environment that starts your agent and declare STRADDLE_ENVIRONMENT=sandbox. If you use STRADDLE_BASE_URL, set it to https://sandbox.straddle.com. The Wizard reads key presence and declared environment from these shell variables. A key saved only in the Straddle CLI’s credential configuration needs to be supplied to the agent’s environment as well. MCP discovery shows that your agent can find the server’s tools. Use the setup report’s authenticated-read result to check whether the key authorizes the requested API operation. These results appear separately in the report.

Start the integration

Once the project is ready, run the full program:
The program runs Setup, Plan, Integrate, Test, and Go Live readiness. It adds Migrate after Plan when it detects another payment provider.

Run and resume

Follow the plan, approvals, and reports through an integration.

Choose a focused command

Run planning, testing, migration, or review on its own.