Capping Spend for Callers of Model Proxies

A model wallet identifies a caller of a model proxy and caps that caller’s token or dollar spend against a provider over a set time window. Each wallet has a system-generated client ID and required JSON Web Token (JWT) claims that you define.

When a caller sends a request, the proxy matches the client ID and claims to a wallet and counts the request against that wallet’s budgets. After the wallet reaches its budget, the proxy blocks further requests to that provider’s models. That block enforces a spend or token cap. A wallet doesn’t grant or deny access to the proxy.

Automate model wallet management using the MuleSoft MCP Platform Server. For details, see fetch_model_wallets and related tools in the MuleSoft MCP Platform Server Tool Reference.

Before You Begin

To manage model wallets, you need:

An Anypoint Platform account.
At least one configured model proxy. See Creating Model Proxies.
A configured identity provider (IdP) that issues JWTs for callers.
Policies configured on each model proxy that callers reach through the wallet. See Configure Policies on a Model Proxy.
API Manager permissions:
- API Manager: API Creator
- API Manager: View APIs Configuration
- API Manager: Edit APIs Configuration
- API Manager: Manage Policies, to apply, disable, reorder, and edit policies
For more information, see Enhanced Experience Permissions.

Organizations without an IdP configured can’t use model wallets. Those organizations continue to use existing access methods.

Configure Policies on a Model Proxy

A model wallet matches the client ID and JWT claims in a request to the wallet’s configuration. Default model proxy policies include DataWeave Headers Transformation and Client ID Enforcement. For wallets, disable those policies and identify callers from the JWT.

Apply these policy changes on each model proxy that callers reach through the wallet. Apply them from the model proxy, not from Model Wallets.

From Portfolio > Model Proxies, open the model proxy.
Select the Policies tab.
From the actions menu for DataWeave Headers Transformation inbound policy, select Disable Policy.
From the actions menu for the Client ID Enforcement inbound policy, select Disable Policy.
Select Apply Policy.
Select JWT Validation, and then select Next.
Configure the policy to validate tokens from your IdP, including the JWT origin and the JSON Web Key Set (JWKS) URL or signing key. For configuration parameters, see JWT Validation policy.
Select Apply Policy.
Select Reorder Instance Policies.
Move JWT Validation to the second position.

The Cross-Origin Resource Sharing policy remains first. JWT Validation in the second position validates the token before later policies read the claims.
Select Save Order.
From the actions menu for LLM Proxy Core Policy, select Edit Configuration.
In Client ID, enter:
```
#[authentication.properties.claims.client_id]
```
This expression reads the client_id claim after JWT Validation publishes the verified claims.
Select Save Changes.

Repeat these policy steps for each model proxy that callers reach through the wallet.

Create a Model Wallet

Create a model wallet to name the wallet, select an environment, define the JWT claims that identify callers, and add at least one budget. A business group can have up to 50 model wallets.

To create a model wallet, you need:

A model proxy.
A configured identity provider (IdP) that issues JWTs for callers.
Policies configured on each model proxy that callers reach through the wallet. See Configure Policies on a Model Proxy.
Costs configured for the models that callers use through the wallet. For more information, see Setting Model Costs for Spend Tracking.
1. From Portfolio > Model Proxies > Model Wallets, select New Model Wallet.
2. In Name, enter a name for the wallet, for example, Finance Analytics Bot.
3. (Optional) Enter a Description of the wallet’s purpose.
4. Under Authentication, copy the system-generated Client ID.
  
  The Client ID is read-only. The service selects a wallet by matching the caller’s JWT claims against each wallet’s required claims. The matching wallet with the highest priority wins. Client ID is only a tie-breaker. When several wallets share the best matching priority, send the optional x-client-id request header to select the tied wallet whose Client ID equals that value. If the header is absent or matches none of the tied wallets, the service uses the tied wallet whose Client ID sorts first alphabetically.
5. In Required Claims, enter at least one required claim:
  In Claim key, enter one or more claim keys, for example, group.
  
  In Claim values, enter one or more comma-separated values.
  
  To add more claims, select Add Claim again.
  The required claims match claims in the JWT after the JWT Validation policy on the model proxy validates the token.
6. Click + Add Budget to add one or more budgets for this model wallet to cap spend or token usage. See Add a Budget to a Wallet.
7. Select Create Model Wallet.

View Model Wallets

From Portfolio > Model Proxies, select Model Wallets. The wallet list shows:

Name: The wallet’s display name.
Description: The wallet’s purpose.
Budgets: The number of budgets on the wallet.
Last Updated: When the wallet was last changed.

To find a specific wallet, use the search box to filter by name or description.

Edit a Model Wallet

From Portfolio > Model Proxies > Model Wallets, open the wallet and select Edit.
Change the Name, Description, or Required Claims.

The Client ID is read-only.
Select Save.

Manage budgets separately from the wallet name, description, and claims. See Add a Budget to a Wallet.

Add a Budget to a Wallet

A budget caps usage for a wallet against a provider and a model over a recurring period. Add a budget when you create or edit a model wallet, or add a budget from the budgets view in Governance > Cost Management.

Open the model wallet from Portfolio > Model Proxies > Model Wallets, or open the budgets view in Governance > Cost Management.
In the Budgets section, select Add Budget.
Enter the budget details:
- Model Wallet: The wallet you’re adding the budget to. This value is already set.
- Provider: Select an LLM provider.
- Model: Select the model to apply the budget to. This field stays unavailable until you select a provider.
- Period: Select Daily, Weekly, or Monthly.
- Metric: Select Spend to set a dollar limit, or Tokens to set a token count limit.
- Spend Limit (USD) or Token Limit: Enter the maximum allowed value. The field label matches the metric.
Select Add Budget.

A model wallet can have more than one budget. Each model wallet, provider, and model combination supports only one budget.

Spend-based budgets depend on model costs. To track dollar spend accurately, set a cost for each model on the Models page. Models without configured costs show zero spend. See Setting Model Costs for Spend Tracking.

When usage reaches the budget limit, the model proxy blocks requests for that provider and model. If a fallback route exists, then the model proxy routes the request to the next model in the proxy’s route.

Budgets are approximate rather than a real-time hard cutoff. The model proxy tracks total token consumption across routes as a governance and cost-awareness tool. Usage can briefly exceed a limit before the model proxy blocks requests.