Bundler wallet status and balance

The bundler wallet is the externally owned account that submits sponsored advanced-accounts transactions on chain. It pays the native gas for each bundle it settles, so its balance is an operational health signal: when it runs dry, sponsored user operations stop landing. These two read-only endpoints report whether the bundler wallet is provisioned for the active system and how much native token it currently holds.

Use them when a dashboard, support runbook, or monitoring integration needs to watch bundler funding alongside paymaster deposits and gas treasury runway.

Requires: advanced accounts enabled for the deployment, and a caller with the administrator, system manager, auditor, or gas manager role for the active system.

This surface is distinct from the bundler JSON-RPC endpoint, which submits and tracks UserOperations. For the paymaster that sponsors gas, see Gas sponsorship paymasters. For how the bundler buffer and paymaster deposit refill from settlement refunds, see Gas treasury runway and fee split.

Access and scope

Authenticate every request with an organization context. Server integrations send the X-Api-Key header shown in the examples; browser or session integrations can use an authenticated user session through the standard cookie or authorization flow.

Both endpoints resolve the bundler wallet for the active organization. A caller without the administrator, system manager, auditor, or gas manager role on the active system receives an authorization error and no wallet data.

Endpoint summary

Read the wallet status

The status endpoint reports whether a bundler wallet is provisioned for the organization. The endpoint always returns a result: when no wallet is configured, address is null rather than an error. Read the status to confirm advanced-accounts setup before relying on the balance read.

curl --request GET \
  "$DALP_API_URL/api/v2/system/bundler/status" \
  --header "X-Api-Key: $DALP_API_TOKEN"

Example response:

{
  "data": {
    "address": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F"
  },
  "links": {
    "self": "/v2/system/bundler/status"
  }
}

When no bundler wallet has been configured, address is null:

{
  "data": {
    "address": null
  },
  "links": {
    "self": "/v2/system/bundler/status"
  }
}

Treat null as "not yet provisioned," not as an error. The balance endpoint returns a configuration error in the same state, so check status first when a monitoring path needs to distinguish an unconfigured system from a funded but empty wallet.

Read the wallet balance

The balance endpoint reads the bundler wallet's native token balance directly from the chain at request time. The value is the wallet's own native balance, the gas it spends to settle bundles, not a paymaster EntryPoint deposit. For the EntryPoint deposit that funds sponsorship, use Gas sponsorship paymasters.

curl --request GET \
  "$DALP_API_URL/api/v2/system/bundler/balance" \
  --header "X-Api-Key: $DALP_API_TOKEN"

Example response:

{
  "data": {
    "address": "0x71C7656EC7ab88b098defB751B7401B5f6d8976F",
    "balance": "2500000000000000000",
    "nativeTokenSymbol": "ETH"
  },
  "links": {
    "self": "/v2/system/bundler/balance"
  }
}

Parse balance as a big integer. The wei-denominated string never loses precision in transit, and dividing by 10^18 in the display layer converts it to whole native tokens.

When the wallet is not configured

When no bundler wallet is provisioned for the organization, the balance endpoint returns error DALP-0239 with HTTP status 503. The error is retryable and clears once a bundler wallet is configured for the system. Call GET /api/v2/system/bundler/status first to confirm provisioning before treating a balance failure as an incident.

Operational notes

• These are status reads, not funding guarantees. A non-zero balance does not promise that the next bundle settles, only that the wallet held that amount at read time.
• Read balance as a big integer string and keep precision until the display layer.
• A null status address and a DALP-0239 balance error describe the same unconfigured state from two endpoints. Surface them as "not configured," not as a depleted wallet.
• Pair this read with the paymaster deposit balance and gas treasury runway to see the full sponsored-gas funding picture.

Related guides

• Bundler for submitting and tracking UserOperations through the ERC-4337 JSON-RPC endpoint.
• Gas sponsorship paymasters for paymaster EntryPoint deposits and sponsorship configuration.
• Gas treasury runway and fee split for how the bundler buffer and paymaster deposit refill from settlement refunds.
• Advanced accounts concept for the account-abstraction model behind sponsored transactions.