Subscription Usage

The Subscription Usage request returns the total number of resources, projects, environments, domains, and so on, created in your organization for a specific service. Pass the service you want data for in the services parameter: launch, cs-assets, or agents. For CMS and Automate figures, use the Usage Analytics request.

NoteThe shape of data differs by service. For launch, data is an array containing a single object. For cs-assets and agents, data is a single object.

Here’s how your response body would look like when you pass the jobId in the Retrieve Data endpoint with services set to launch.

{
    "data": [
        {
            "total_launch_project": 9,
            "total_launch_env": 11,
            "total_launch_domain": 2
        }
    ],
    "meta": {
        "orgUid": "blt**************87",
        "from": "2024-06-30",
        "to": "2024-09-12"
    },
    "uid": "0f****46-5ee9-4f38-9146-1f********87"
}

The response body provides an overview of the resources in the Launch section within your organization. Here’s a breakdown of the key elements:

• total_launch_project: The total number of projects created within Launch.
• total_launch_env: The total number of environments associated with the Launch projects .
• total_launch_domain: The total number of domains configured within Launch.

This response gives a clear view of how Launch resources are utilized within the specified date range.

Here’s how your response body would look like with services set to cs-assets.

{
    "data": {
        "deleted_assets_total": 0,
        "workspace_total": 0,
        "asset_storage": 9932858,
        "asset_total": 14,
        "ai_assets_usage": 0,
        "spaces_total": 0,
        "fields_total": 0,
        "custom_asset_types": 0
    },
    "meta": {
        "orgUid": "blt**************cc",
        "date": "2026-05-19",
        "services": "cs-assets"
    },
    "uid": "cf****06-c2e4-48e6-a776-af********95"
}

Field reference:

• custom_asset_types: Number of custom asset types defined in the organization.
• workspace_total: Total number of workspaces in the organization.
• deleted_assets_total: Total number of assets deleted in the organization.
• spaces_total: Total number of spaces in the organization.
• asset_total: Total number of assets stored in the organization.
• asset_storage: Total storage consumed by assets.
• ai_assets_usage: Total AI-assisted asset operations performed in the organization.
• fields_total: Total number of custom fields defined across asset types.

Here’s how your response body would look like with services set to agents.

{
    "data": {
        "agent_executions_completed": 0,
        "agent_total": 0,
        "total_tokens_consumed": 0,
        "agent_executions_failed": 0,
        "total_executions": 0,
        "total_active_agents": 0
    },
    "meta": {
        "orgUid": "blt**************74",
        "date": "2026-05-19",
        "services": "agents"
    },
    "uid": "dc****76-a481-4c7b-b944-63********fb"
}

Field reference:

• agent_total: Total number of agents in the organization.
• total_active_agents: Number of agents currently in an active state.
• total_executions: Total number of agent executions, including completed and failed runs.
• agent_executions_completed: Number of agent executions that completed successfully.
• agent_executions_failed: Number of agent executions that failed.
• total_tokens_consumed: Total number of LLM tokens consumed across all agent executions.