> ## Documentation Index
> Fetch the complete documentation index at: https://docs.straddle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set account scope

> Choose when to send Straddle-Account-Id for direct, SaaS, and marketplace requests.

Set account scope for each API MCP request. The `Straddle-Account-Id` header names the embedded account a platform acts for; whether to send it depends on your integration model and the operation.

Set the account in your MCP request separately from the account selected in the Straddle CLI.

## Choose the account

For a platform request, use the Straddle account ID from your application's tenant mapping or an exact account lookup. Resolve an ambiguous match before continuing. For the account model itself, see [Manage embedded accounts](/guides/embed/accounts).

Keep the following facts together when reviewing a request:

| Fact | Example |
| - | - |
| Environment | Sandbox, `https://sandbox.straddle.com` |
| Integration model | SaaS |
| Selected account | The sandbox account ID you supplied |
| Operation | `GET /v1/charges/{id}` |
| Header | `Straddle-Account-Id` set to that account ID |

Confirm the integration model in your platform configuration and integration plan.

## Apply the header rule

Use the following rules for the request you discovered:

| Operation | Direct account | SaaS | Marketplace |
| - | - | - | - |
| Create customer, create paykey through Bridge, initialize Bridge | Omit | Required | Omit |
| Other customer and paykey reads and updates | Omit | Send when an account is selected | Omit |
| Create charge or payout, refund, resubmit, upload charge authorization | Omit | Required | Required |
| Other charge, payout, funding-event, and payment reads and updates | Omit | Send when an account is selected | Send when an account is selected |
| Organizations, accounts, account settings, representatives, linked bank accounts, onboarding | Omit | Omit | Omit |

When a SaaS or marketplace row says “send when an account is selected,” omit the header if no account is selected. Select the account explicitly for a task about one tenant.

Marketplace customers and paykeys belong to the platform, so their requests omit the header. Charges and payouts identify the seller's account when the operation requires it.

## Pass scope to API MCP

For an account-scoped request, include the selected ID in `execute-request`'s `headers`. Replace the placeholder with the account you confirmed:

```json theme={null}
{
  "Straddle-Account-Id": "<selected-account-id>"
}
```

For account-management operations such as `GET /v1/accounts/{account_id}`, the path identifies the account and the header stays omitted.

## Switch to another account

Confirm the new account ID, review the operation's header rule, and rebuild the request before sending it. Any write preview must show the new target before you approve it.

For a first authenticated read, follow [Read an account through API MCP](/developer-tools/mcp/api-requests).


## Related topics

- [Connect your agent to Straddle](/developer-tools/mcp/overview.md)
- [Create a Mastercard token for Straddle](/integrations/open-banking/mastercard.md)
- [Troubleshoot the Straddle CLI](/developer-tools/cli/troubleshooting.md)
- [Quiltt integration for ACH payments](/integrations/open-banking/quiltt.md)
- [Choose an SDK](/developer-tools/sdks.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.