Before you start
Prepare the following:- Connect API MCP with a sandbox API key.
- Choose an existing sandbox account ID that your key can read.
- Confirm the request host is
https://sandbox.straddle.com.
Straddle-Account-Id for every integration model.
Discover and run the read
1
Find the operation
Ask the agent to discover the account read and show you its inputs:Discovery returns the operation’s schema for your review before execution.
Find the sandbox account read.
2
Review the request
Check the proposed values:
Your client supplies the bearer token. Keep the key out of the prompt and tool arguments.
3
Run the read
Confirm the proposed request and let the agent call
execute-request once. Review the client’s tool approval prompt if it appears.Ask the agent to report the HTTP status, returned account ID, account status, and request ID when available. Keep personal and business details out of the summary unless your task needs them.4
Inspect the result
A successful response verifies access to that sandbox account with the configured key. Confirm the returned account ID matches the one you selected.For a failed response, keep the status and request ID and follow MCP troubleshooting.
Use current Scalar IDs
Take both IDs fromsearch-openapi-operations in the same session. Contract publication can change them.
The OpenAPI operationId, such as getAccount, is a human-readable name. execute-request needs the Scalar UUID from x-scalar-operation-id.
Adapt the workflow
For another read, discover that operation’s schema and review its parameters first. Put query parameters inpath, for example /v1/accounts?page_size=1. Apply the account-scope rules for the resource and integration model.
For implementation and sandbox writes, use the Straddle skills. They prepare request previews and choose the SDK, CLI, or API MCP route for each operation. Authentication and permissions explains those choices.