# Set up Track Month End Close

This is a read-only composite, but it needs a model credential and every listed data source configured before it can run. Set up isolated test accounts or workspaces first, grant only the smallest read scope that exposes the test data, and store every credential only in Dome's secret inputs. Never put a key or secret in this repository, an agent prompt, or a chat message.

## Create the model credential

- Create an API key in the [Anthropic Console](https://console.anthropic.com/settings/keys).
- Enter the raw key as `anthropic_api_key` during import. Do not prepend `Bearer `.
- The template uses that key only for its managed `claude-sonnet-5` model connection.

## Create the provider credentials

- No provider secret is required before import. The connected providers below use browser OAuth with Dynamic Client Registration.

For a provider that asks you to register a manual OAuth app, use this callback URL exactly:

`https://api.domesystems.ai/oauth/callback`

## Set up each connected provider

### Stripe

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

This composite uses Stripe OAuth. It only exposes documentation and API-metadata
tools, not generic account-read or write tools.

1. Import the template with `anthropic_api_key`; no Stripe API key is required.
2. In Dome, open the `stripe` tool connection and select **Authorize**.
3. Sign in to Stripe, select the sandbox account to authorize, and approve the
   `mcp` scope.
4. Confirm that the connection is reachable, then use a managed run to ask a
   documentation or API-schema question.

You can revoke the connection later from Stripe's **OAuth sessions** settings.
Use a separate, reviewed template before granting account-data reads or writes.

### Ramp

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

After saving, authorize a test user with reporting access only. Do not connect an identity that can approve expenses, reimburse, create cards, or change controls.

### Brex

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

Before connecting, a Brex account or card admin must accept the Developer API agreement in **Settings → Developer** and enable **Brex in AI assistants** under **Settings → Beta features**. The MCP server then registers the OAuth client dynamically; authorize a test Brex user with reporting access only. Do not use an identity that can issue cards, approve expenses, move money, or change policies.

### Mercury

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

After saving, authorize a test Mercury user with minimum account-viewing access. Do not connect an identity that can originate or approve transfers or administer accounts.

### Plaid

This provider uses Dynamic Client Registration (DCR). Do **not** create or paste an OAuth client ID or client secret: after import, Dome registers the client and opens the provider's consent page.

After saving, authorize a test Plaid dashboard user with the lowest role needed for the intended account and connection data. Treat returned financial information as sensitive.

## Import and verify

1. Import the template and provide the values above.
2. Complete every browser OAuth flow with the intended dedicated test user. Token-based sources do not open a browser.
3. Open **Tools**, refresh discovery, and confirm every connection is attached to the template gateway.
4. Run the managed agent against known test data. Treat the template as verified only when the run succeeds **and calls at least one expected read-only tool**.

If a connection is unreachable, check the provider section above for its callback, API/MCP enablement, token prefix, consent scopes, and user/workspace access before retrying.