All servers / Cloud / DoiT MCP server
DoiT MCP server
DoiT official MCP Server
Tested by ConnectATDScore 87 out of 100. Tested 2026-11-18 on package version 5.1.0. Package: @doitintl/doit-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 17 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.0 seconds including download)
- Tools offered: 285
- Last published: 2026-11-18
- Weekly downloads (npm): 5,244
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
get_cloud_connect_requirements4 of 5 parameters describedResolve fresh customer-specific AWS, GCP or Azure Cloud Connect prerequisites, identity trust, per-feature permissions, inputs and deployment artifacts. Read-only. Azure management-group requirements return an inline Azure CLI plan/apply script with exact selected roles and a customer binding; it grants access without registering and does not elevate the operator. GCP organization, project and dataset scopes use the returned inline shell artifact. AWS account scopes return the account CloudFormation template and per-account Terraform module. AWS organization scopes return one management StackSet artifact with entrypoint, a flat files list (path, URL and SHA-256 for both templates) and parameters for one root/OU; no fleet connection or rollout operation is created. AWS membership, Organizations/StackSets prerequisites, deployment success and access remain separate checks. AWS organization real-time bucket/enrollment configuration is unsupported by the pinned artifact. Artifacts are reference implementations for adaptation to customer tooling; their requirements and registration behavior remain relevant when adapted. The selected artifact's requirementsSatisfied and findings determine artifact readiness; feature-level flags or preconditions alone do not. Discovery and blocked artifacts have requirementsSatisfied=false and empty parameters. Returned parameters preserve the artifact's exact spelling and structure. Does not enable billing exports. Full Cloud Connect workflow: MCP resource skill://doit-cloud-connect/SKILL.md.
list_cloud_connections4 of 5 parameters describedDiscover existing Cloud Connect records by structured provider, scope and featureId filters. Pass provider azure or gcp, or that provider’s exact scope, for non-AWS discovery; omitting both provider and scope defaults to AWS. An empty list means no matching registration, not that cloud resources are absent. Subsequent pages use pageToken with the same filters.
get_cloud_connection1 of 1 parameter describedRead a connection's bindings, desired features, last verification summary and named follow-ups. Returns the etag for conditional writes. Stored state is not a fresh access probe; fresh checks are available through verify_cloud_connect.
register_cloud_connection3 of 4 parameters describedRegister a deployed AWS IAM role, GCP service account or Azure DoiT enterprise application explicitly when the final deployment does not register it automatically and no connection exists yet. For AWS, retained DoiT Terraform provider resources and CloudFormation callbacks perform registration through their own workflow; an additional registration duplicates that operation. An existing connection for the scope returns 409 connection_exists; changes to that record use a conditional update. Fresh requirements describe prerequisites, and dry_run_cloud_connection_change previews the request. GCP setup scripts grant access but do not register: use descriptor metadata and the selected GCP scope. Azure uses identity.kind azure_service_principal with tenantId and one management-group binding; the live selected grants must carry the setup-written customer binding. The response returns the authoritative connection id, bindingId and registered scope identifiers for subsequent operations. Registration records an existing cloud target; it does not create an account, project, organization or Azure tenant/group. Registration alone does not establish feature readiness or data arrival. Full Cloud Connect workflow: MCP resource skill://doit-cloud-connect/SKILL.md.
update_cloud_connection5 of 5 parameters describedChange a binding's desired features/inputs, or retry failed follow-ups by re-sending the current desired state. Requires the latest connection etag; 412 indicates a stale value and a change that needs re-evaluation. dry_run_cloud_connection_change previews the exact request and its effects, including removals. Does not change IAM or the identity. Full Cloud Connect workflow: MCP resource skill://doit-cloud-connect/SKILL.md.
remove_cloud_connection4 of 4 parameters describedDisconnect the DoiT record using its exact etag and cleanupScope doit_only; customer IAM/IaC cleanup remains separate. dry_run_cloud_connection_change previews removal effects. 204 means the record is gone; a 409 cleanup_failed keeps it, and another removal attempt requires a fresh etag. A later 404 means already absent. Full Cloud Connect workflow: MCP resource skill://doit-cloud-connect/SKILL.md.
dry_run_cloud_connection_changeno parametersValidate a register, update or remove request and run available live checks without committing (dryRun=true). A new, unregistered AWS role returns aws_broker_requires_registration because the broker cannot probe it before registration; this result does not verify access. Returns preconditions, DoiT side effects, follow-ups and customer cleanup for review. wouldApply is informational, not a reservation or approval. Full Cloud Connect workflow: MCP resource skill://doit-cloud-connect/SKILL.md.
verify_cloud_connect3 of 3 parameters describedRun fresh synchronous access checks for a registered connection. Results include authentication, per-feature checks and coverage, and `recorded` indicating whether the observation was stored. partial, not_checked and failed checks are not passed; a failed authentication leaves every feature not_checked. AWS declared-policy checks do not prove effective access. GCP checks effective scope permissions; BigQuery dataset results expose sampled table coverage. Azure checks fresh management-group access and unconditional role assignments held by the DoiT application at that exact scope; this does not evaluate every effective permission or deny assignment. Access never proves billing data arrived. Nothing is stored as a run; requestId provides correlation. Full Cloud Connect workflow: MCP resource skill://doit-cloud-connect/SKILL.md.
get_cloud_overviewno parametersUse this when the user wants a high-level overview or dashboard of their entire cloud infrastructure. Returns cost by cloud provider, top services per cloud, top projects per cloud, recent cost anomalies, and recent cloud incidents — all in a single call. Costs cover the last 30 days including today as totals per cloud, per service, and per project (no daily rows); services and projects are limited to the top 5 values per cloud across that range. Returns at most 5 anomalies and 5 AWS/Google Cloud provider incidents (not account-specific incidents). Failed sections silently return empty arrays, so empty data does not establish zero spend or no incidents. Do NOT use this for detailed drill-downs (use run_query), single-provider analysis, or anomaly-only queries.
get_cloud_incidents3 of 3 parameters describedUse this when the user wants to check for active cloud platform outages, service disruptions, or incidents from AWS or Google Cloud. Both active and archived incidents are included unless status is filtered. Do NOT use this for cost anomalies (use get_anomalies) or support tickets (use list_tickets).
get_cloud_incident2 of 2 parameters describedUse this when the user wants to view details of a specific cloud platform incident. Accepts either the incident ID or a partial title match (case-insensitive). Do NOT use this for listing all incidents (use get_cloud_incidents) or anomalies (use get_anomalies).
get_anomalies1 of 1 parameter describedUse this when the user wants to check for unexpected cost spikes, billing anomalies, or unusual spending patterns. Returns recent anomalies with severity and impact. Do NOT use this for optimization recommendations or savings opportunities (use list_optimization_recommendations), regular cost analysis (use run_query), or viewing alerts (use list_alerts).
get_anomaly1 of 1 parameter describedUse this when the user wants to view details of a specific cost anomaly by its ID. Returns full anomaly data including affected resources and cost impact. Do NOT use this for listing all anomalies (use get_anomalies).
list_reports3 of 3 parameters describedUse this when the user wants to see their saved Cloud Analytics reports or browse available reports. Returns pages of up to 40 reports with IDs and metadata, newest creation first. rowCount counts this page; pageToken retrieves the next page and is null at the end. Empty results return an error. Supports server-side, case-insensitive partial name filtering through name. Do NOT use this for running queries (use run_query) or getting report results (use get_report_results).
run_query1 of 1 parameter describedUse this when the user wants to analyze cloud costs, generate a cost breakdown, view spending trends, or run a custom analytics query across their cloud providers. Runs the config through the DoiT Cloud Analytics API query endpoint (https://developer.doit.com/reference/query) and returns the result rows. Accepts a structured config with data source, metrics, dimensions, time range, and filters. Do NOT use this for listing saved reports (use list_reports), checking anomalies (use get_anomalies), or viewing budgets (use list_budgets). Unpopulated fields take API defaults: basic cost, last 7 days including today, daily time rows (year/month/day), and billing (or billing-datahub for customers with DataHub metrics). Each `config.group[].limit.value` selects top/bottom N dimension values per parent group, ranked across the range; it does not cap result rows and has no tool-enforced maximum of 25. Time columns can produce multiple rows per group. `timeRange` covers relative periods; explicit dates require `timeRange: {mode: "custom"}` and sibling `config.customTimeRange: {from, to}`, with no unit. For mode "last", "includeCurrent": true includes the current partial period within amount; false selects fully completed periods. One month with true is current month-to-date. "metrics" (array) supersedes the deprecated "metric" (object). A "group" with id "service_description" and type "fixed" returns a per-service cost breakdown, the most common shape for cost questions. Common grouping dimension IDs (all type "fixed"): "service_description" — cloud service "project_id" — GCP project / AWS account / Azure subscription "cloud_provider" — cloud provider (AWS / GCP / Azure) In default mode "is", filter values must exactly match stored dimension values (case-sensitive): cloud_provider uses provider IDs, while service_description uses service names. Common cloud-provider aliases such as aws/gcp/azure are normalized by run_query. get_dimension({type, id}) returns the valid values for a dimension for this customer. Known cloud provider IDs (cloud_provider, type "fixed"): "amazon-web-services" = AWS, "google-cloud" = GCP, "microsoft-azure" = Azure Example — top AWS services last month: { "config": { "dataSource": "billing", "metrics": [{"type": "basic", "value": "cost"}], "timeRange": {"mode": "last", "amount": 1, "unit": "month", "includeCurrent": false}, "filters": [{"id": "cloud_provider", "type": "fixed", "values": ["amazon-web-services"]}], "group": [{"id": "service_description", "type": "fixed", "limit": {"metric": {"type": "basic", "value": "cost"}, "sort": "desc", "value": 10}}] } }
cost_breakdown4 of 4 parameters describedUse this when the user wants a simple cost breakdown by service, project, or cloud provider (e.g. 'What are my top services by cost?', 'Which projects cost the most?'). Selects the top-N groups by total cost across the range and returns monthly rows for each. The range includes the partial current month; months=1 means month-to-date. Output row order is not a cost ranking. For complex multi-filter or multi-metric queries, use run_query instead.
cost_trend4 of 4 parameters describedUse this when the user wants to see monthly spend over time (e.g. 'Show me my cost trend', 'How has my spend changed over the last 6 months?'). Returns monthly cost data points, optionally broken down by service/project/cloud. The last point is the partial current month; months=1 means month-to-date. For daily granularity or custom time intervals, use run_query instead.
compare_spend4 of 4 parameters describedUse this when the user wants to compare spend between two time periods (e.g. 'Compare the latest three months including this month with January through March'). Period 1 is N-1 full calendar months plus current month-to-date; period 2 is an explicit date range. Returns two separate sets of monthly rows, each independently limited to its top 10 groups across that period. Groups can differ; no difference or percentage change is computed. For more than two periods or advanced comparative analysis, use run_query instead.
list_optimization_recommendations10 of 10 parameters describedUse this when the user asks about optimization, recommendations, insights, savings opportunities, rightsizing, idle resources, security findings, or cost reduction suggestions. Also use this when the user asks 'what insights are available?' or 'show me insights'. This is the primary tool for 'what can I optimize?', 'how can I save money?', and 'what insights do I have?' questions. Returns insights ordered within each page by estimated daily savings, not priority. All statuses are included unless filtered, including dismissed. easyWin is derived from easyWinDescription when present, otherwise null. Follow pageToken for more results. Do NOT use this for cost anomalies/spikes (use get_anomalies) or budget tracking (use list_budgets).
get_insight_resources4 of 4 parameters describedUse this when the user wants to see which specific resources are affected by an optimization insight. Returns a page of resourceResults with rowCount and pageToken, resource IDs, accounts, savings or risk counts. There is no dedicated remediation field. Default page size is 1000; follow pageToken for more resources. Do NOT use this for listing all insights (use list_optimization_recommendations).
get_insight2 of 2 parameters describedUse this when the user wants the details and aggregate summary (savings, risk counts, status, description) of a single optimization insight identified by its source and key. Returns the insight metadata only — it does NOT include the individual affected resources (use get_insight_resources for those) and is not for listing all insights (use list_optimization_recommendations).
post_insight_result12 of 12 parameters describedUse this when the user wants to create a new custom insight or update an existing one's metadata (title, description, categories, status, remediation links). Only insights owned by the 'public-api' source can be managed (the default source). Requires key, title, shortDescription, cloudProvider and categories on every call. This replaces insight metadata: omitted optional fields such as detailedDescriptionMdx, reportUrl, easyWinDescription and cloudFlowTemplateId are cleared. Affected resources are managed separately (post_insight_resource_results). For a status-only change, use update_insight_status to preserve metadata despite that endpoint's deprecation.
update_insight_status4 of 4 parameters describedUse this when the user wants to change the display status of an existing insight (e.g. mark it acknowledged, in progress, optimized, or dismissed). This endpoint is deprecated but remains the safe choice for status-only changes because it preserves optional insight metadata; post_insight_result replaces it. Only insights owned by the 'public-api' source can be managed. When dismissing, dismissalDetails.reason is required; comment is optional. Do NOT use this to edit an insight's title/description or create one (use post_insight_result).
get_report_results2 of 2 parameters describedUse this when the user wants to retrieve the data results of a specific saved report. Uses the report's saved time range, resolved at execution for relative ranges. Accepts an ID or a case-insensitive substring name lookup within the first 200 newest reports; multiple matches return an ambiguity error and id takes precedence. Do NOT use this for listing all reports (use list_reports) or running ad-hoc queries (use run_query).
get_report_config1 of 1 parameter describedGet the configuration of a specific Cloud Analytics report by ID. Returns the stored report object including name, type, and a nested 'config' field containing data source, metrics, dimensions, time range, filters, and visualization settings.
create_report5 of 5 parameters describedUse this when the user wants to save a new Cloud Analytics report with a specific configuration. Creates a new custom report immediately without replacing existing reports, optionally inside a folder (folderId). Omitted config fields take API defaults: basic cost, last 7 days including today, daily time rows, and billing (or billing-datahub when the customer has DataHub metrics). System labels are rejected. Do NOT use this for one-time queries without saving (use run_query).
update_report6 of 6 parameters describedUse this when the user wants to modify an existing saved Cloud Analytics report. Only custom reports the caller can edit are supported. Supports partial updates with array replacement and config reset semantics described on config. Omitted top-level fields are unchanged; labels replaces non-system labels; folderId moves the report to another folder. Changes apply immediately. Do NOT use this for running ad-hoc queries (use run_query).
validate_userno parametersUse this when the user asks to verify their account connection or check who they are logged in as. Returns the authenticated user's email and the primary domain of the customer the session is scoped to. Authentication is already established by the connection, so other tools do not depend on this call. Do NOT use this for listing users in the organization (use list_users).
list_dimensions2 of 2 parameters describedUse this when the user wants to see available dimensions for cost analysis queries. Returns id, label and type metadata only (no values), up to 200 dimensions per page, sorted by id. GKE dimensions are omitted. pageToken retrieves subsequent pages; rowCount counts this page. get_dimension retrieves values. Empty results return an error. Do NOT use this for running cost queries directly (use run_query) or viewing allocations (use list_allocations).
get_dimension2 of 2 parameters describedUse this when the valid filter values for a specific dimension are needed, such as for a run_query filter, or when the user wants to view dimension details. Returns id, label, type and all available value/cloud pairs in one response, without pagination. For example, get_dimension({type: 'fixed', id: 'cloud_provider'}) returns the exact provider IDs available for this customer. Do NOT use this for listing all dimensions (use list_dimensions) or running queries (use run_query).
list_tickets3 of 3 parameters describedUse this when the user wants to view their support tickets, check ticket status, or review open issues. Returns tickets with status, severity, and platform. Customers see their own tickets; organization tickets are visible when ticket sharing is enabled. Subject filtering is case-insensitive and applies only to the returned page. The API cursor and unfiltered rowCount are preserved, including on pages with no matches. Each ticket's fields array lists only custom fields that have a value; unset fields are omitted. Do NOT use this for cloud incidents (use get_cloud_incidents) or cost alerts (use list_alerts).
get_ticket1 of 1 parameter describedReturns details of a specific support ticket from the DoiT API by its ID.
list_ticket_comments2 of 2 parameters describedReturns all comments on a support ticket. For customers, only public comments are returned. For DoiT employees, both public and private comments are returned.
create_ticket_comment3 of 3 parameters describedAdds a comment to an existing support ticket. For customers, comments are always public. For DoiT employees, comments can be marked as private (internal notes) by setting the private field to true.
create_ticket0 of 1 parameter describedUse this when the user wants to create a new support ticket. The ticket is opened with DoiT support immediately. Do NOT use this for viewing existing tickets (use list_tickets) or cloud incidents (use get_cloud_incidents).
list_invoices1 of 1 parameter describedUse this when the user wants to see their invoices, check billing history, or review payment records. Returns a list of invoices with amounts, dates, and status. Do NOT use this for cost analysis (use run_query) or budget tracking (use list_budgets).
get_invoice1 of 1 parameter describedUse this when the user wants to view details of a specific invoice by its ID. Returns full invoice data including line items and status. Do NOT use this for listing all invoices (use list_invoices) or cost analysis (use run_query).
list_allocations2 of 2 parameters describedUse this when the user wants to see their cost allocation rules or configurations. Returns a list of allocations. Returns pages of 40; pass the returned pageToken for another page (null means no next page). The case-insensitive partial name filter applies only to that returned page. Do NOT use this for cost queries (use run_query) or labels (use list_labels).
get_allocation2 of 2 parameters describedUse this when the user wants to view details of a specific cost allocation. Accepts either the allocation ID or a case-insensitive partial name. Name lookup searches only the first 200 allocations; multiple matches return an error listing names, and id takes precedence. Do NOT use this for listing all allocations (use list_allocations) or running queries (use run_query).
create_allocation5 of 5 parameters describedUse this when the user wants to create a new cost allocation rule. Changes apply immediately. Do NOT use this for viewing existing allocations (use list_allocations) or labels (use create_label).
update_allocation6 of 6 parameters describedUse this when the user wants to modify an existing cost allocation. Omitted fields are preserved. Use rule for an existing single allocation and rules for an existing group; the type cannot change. A supplied rules list replaces the entire group membership. Changes apply immediately. Do NOT use this for creating new allocations (use create_allocation) or viewing allocations (use list_allocations).
list_assets4 of 4 parameters describedUse this when the user wants to browse their cloud assets, subscriptions, or resources. Returns a paginated list of assets. Name filtering is case-insensitive and applies only to the returned page. The API cursor and unfiltered rowCount are preserved, including on pages with no matches. Do NOT use this for cost analysis (use run_query) or checking invoices (use list_invoices).
get_asset2 of 2 parameters describedUse this when the user wants to view details of a specific cloud asset. Accepts an asset ID, which takes precedence over name, or a case-insensitive partial name lookup within the first 249 assets only. Multiple name matches return an ambiguity error. Do NOT use this for listing all assets (use list_assets) or cost analysis (use run_query).
list_alerts5 of 5 parameters describedUse this when the user wants to see their cost alerts or check alert configurations. Returns a paginated list of alerts. Do NOT use this for anomaly detection (use get_anomalies) or budget tracking (use list_budgets).
get_alert2 of 2 parameters describedUse this when the user wants to view the details of a specific cost alert. Accepts either the alert ID or a partial name (case-insensitive). Do NOT use this for listing all alerts (use list_alerts) or anomalies (use get_anomalies).
create_alert4 of 4 parameters describedUse this when the user wants to set up a new cost alert with thresholds and notification settings. Notifies email recipients and/or Slack channels (recipientsSlackChannels). Changes apply immediately. Do NOT use this for creating budgets (use create_budget) or viewing existing alerts (use list_alerts).
update_alert5 of 5 parameters describedUse this when the user wants to modify an existing cost alert. Supports partial updates, including name-only, email or Slack recipients only, or individual config fields. Omitted fields are preserved; scopes: [] and recipientsSlackChannels: [] clear those lists. Changes apply immediately. Do NOT use this for creating new alerts (use create_alert) or budgets (use create_budget).
trigger_cloud_flow2 of 2 parameters describedTriggers a published CloudFlow with a webhook trigger by flow ID or trigger URL. Executes real actions immediately and returns executionLink. Drafts fail with 403, flows without a webhook trigger with 400, and already-running flows with 409. Manual or scheduled flows use trigger_cloudflow_flow instead. This may modify external cloud resources.
list_cloudflows2 of 2 parameters describedUse this when the user wants to see their CloudFlow automation flows. Returns a cursor-paginated list of flows with their metadata, status, and last execution info.
list_cloudflow_connections2 of 2 parameters describedUse this when the user wants to see their CloudFlow cloud provider connections (the GCP/AWS accounts connected for automation). Returns a cursor-paginated list of connections with their config and status. Do NOT use this to trigger a flow (use trigger_cloud_flow) or to view a single connection's details (use get_cloudflow_connection).
get_cloudflow_connection1 of 1 parameter describedUse this when the user wants to view the details of a specific CloudFlow cloud provider connection by its ID, including its GCP/AWS configuration, collaborators, and status. Do NOT use this to list all connections (use list_cloudflow_connections) or to trigger a flow (use trigger_cloud_flow).
create_cloudflow_connection7 of 7 parameters describedUse this when the user wants to create a new CloudFlow cloud provider connection (a GCP or AWS account connected for automation). Exactly one of gcpConfig or awsConfig must be supplied. Changes apply immediately. Do NOT use this to update an existing connection (use update_cloudflow_connection) or to trigger a flow (use trigger_cloud_flow).
update_cloudflow_connection8 of 8 parameters describedUpdates a CloudFlow connection immediately using connectionId and the last observed ETag (ifMatch). A stale ETag fails with 412. Other fields are optional; supplied gcpConfig/awsConfig and collaborators replace their stored values wholesale. Retain exactly one owner when replacing collaborators. At most one provider config may be supplied. Serialize updates because the API version check is not atomic with the write. If an HTTP failure has only generic text, do not infer its status or retry automatically.
list_cloudflow_templates2 of 2 parameters describedUse this when the user wants to see the catalogue of available CloudFlow templates (read-only blueprints they can build a flow from). Returns a cursor-paginated list of templates with their id, name, description, and instructions. Do NOT use this to view a single template's details (use get_cloudflow_template) or to trigger a flow (use trigger_cloud_flow).
get_cloudflow_template1 of 1 parameter describedUse this when the user wants to view the details of a specific CloudFlow template by its ID, including its name, description, and configuration instructions. Do NOT use this to list all templates (use list_cloudflow_templates) or to trigger a flow (use trigger_cloud_flow).
refine_cloudflow3 of 3 parameters describedRefines an existing CloudFlow using natural language. Streams progress and returns the answer and conversationId; normally no flowId is returned. A plan or clarification question may save nothing. Reusing conversationId continues that conversation. Generated codeNode code can pass validation and fail silently or error at run time, so a successful build shows only that a draft was saved. export_cloudflow_flow returns the saved code; a completed test run's per-node output shows whether it works. Test runs execute real actions, including on drafts. Full CloudFlow authoring guide: MCP resource doit://docs/cloudflow-authoring.
build_cloud_flow2 of 2 parameters describedUse this when the user wants to build a brand-new CloudFlow automation from scratch using natural language. Creates the draft before planning, so flowId can be returned even if the builder stops early. Streams progress and returns flowId, conversationId, the answer, and any build steps. Reusing conversationId continues the conversation but this endpoint still creates a new draft; refine_cloudflow targets an existing flow. Generated codeNode code can pass validation and fail silently or error at run time, so a successful build shows only that a draft was saved. export_cloudflow_flow returns the saved code; a completed test run's per-node output shows whether it works. Test runs execute real actions, including on drafts. Full CloudFlow authoring guide: MCP resource doit://docs/cloudflow-authoring.
list_organizations1 of 1 parameter describedUse this when the user wants to see the organizations in their DoiT account. Returns a list of organizations. Do NOT use this for listing users (use list_users) or platforms (use list_platforms).
list_platforms1 of 1 parameter describedUse this when the user wants to see the support-ticket platform catalog. Returns platform IDs and display names for create_ticket; this catalog does not list connected cloud accounts. Do NOT use this for cloud incidents (use get_cloud_incidents) or products (use list_products).
list_users1 of 1 parameter describedUse this when the user wants to see users in their DoiT organization or check who has access. Includes active users and pending invitations. Returns roleId values, which resolve to role details in list_roles. Do NOT use this for listing roles (use list_roles) or validating the current user (use validate_user).
update_user8 of 8 parameters describedUse this when the user wants to update a user's information such as name, job function, phone, language, or role. Changes apply immediately. Do NOT use this for inviting new users (use invite_user) or listing users (use list_users).
invite_user3 of 3 parameters describedUse this when the user wants to invite a new person to the organization. The invitation email is sent immediately. Omitted roleId defaults to Support User. The email domain must be permitted by the customer's invitation policy; existing users and pending invitees cannot be re-invited. Do NOT use this for updating existing users (use update_user) or listing users (use list_users).
list_roles1 of 1 parameter describedUse this when the user wants to see available roles in their DoiT organization. Returns a list of roles with permissions. Do NOT use this for listing users (use list_users) or organizations (use list_organizations).
list_products2 of 2 parameters describedUse this when the user wants to see the support-ticket product catalog for one platform. Returns product IDs, display names, and platform IDs. create_ticket uses the product displayName and the platform ID. Requires platform: the full catalog spans several hundred products across all platforms and exceeds the MCP result size limit, so products are listed one platform at a time. Customers do not see private products. This catalog does not list products purchased by the account. Do NOT use this for cloud incidents (use get_cloud_incidents) or platforms (use list_platforms).
list_labels5 of 5 parameters describedUse this when the user wants to see their DoiT console labels for organizing reports, budgets, alerts, allocations, metrics and annotations. Returns label metadata; these are not cloud resource labels. Do NOT use this for annotations (use list_annotations) or label assignments (use get_label_assignments).
get_label2 of 2 parameters describedUse this when the user wants to view details of a specific DoiT console label (not a cloud resource label). Accepts either the label ID or a case-insensitive partial name. Name lookup searches only the first 200 labels; multiple matches return an error listing names, and id takes precedence. Do NOT use this for listing all labels (use list_labels) or annotations (use list_annotations).
create_label2 of 2 parameters describedUse this when the user wants to create a new DoiT console label for organizing analytics objects. Names must be unique within the customer. Requires Cloud Analytics Admin. Changes apply immediately. Do NOT use this for viewing existing labels (use list_labels) or annotations (use create_annotation).
update_label3 of 3 parameters describedUse this when the user wants to modify an existing custom DoiT console label. Requires Cloud Analytics Admin; preset labels cannot be edited. Supports partial updates; null leaves a field unchanged. Changes apply immediately. Do NOT use this for creating new labels (use create_label) or annotations (use update_annotation).
get_label_assignments2 of 2 parameters describedUse this when the user wants to see which DoiT console objects are assigned to a label. Returns objectId and objectType pairs, without object details. Do NOT use this for viewing label details (use get_label) or allocations (use list_allocations).
assign_objects_to_label3 of 3 parameters describedUse this when the user wants to assign or unassign DoiT console objects (reports, budgets, alerts, allocations, metrics or annotations) to a custom console label. Preset labels cannot be assigned. Requires edit permission on every object; validation is all-or-nothing. add/remove modify associations, not a replacement list. Changes apply immediately. Do NOT use this for creating labels (use create_label) or viewing assignments (use get_label_assignments).
list_folders2 of 2 parameters describedUse this when the user wants to see their Cloud Analytics folders, which organize reports and allocations into a hierarchy. Returns a list of folders with their metadata. Do NOT use this for listing reports (use list_reports) or labels (use list_labels).
get_folder2 of 2 parameters describedUse this when the user wants to view details of a specific Cloud Analytics folder. Accepts either the folder ID or a case-insensitive partial name. Name lookup searches only the first 200 folders; multiple matches return an error listing names, and id takes precedence. Do NOT use this for listing all folders (use list_folders) or viewing reports (use get_report_config).
create_folder3 of 3 parameters describedUse this when the user wants to create a new Cloud Analytics folder to organize reports and allocations. A duplicate sibling name or invalid parent is rejected. Changes apply immediately. Do NOT use this for creating reports (use create_report) or labels (use create_label).
update_folder4 of 4 parameters describedUse this when the user wants to rename, re-describe, or move (reparent) an existing Cloud Analytics folder. Changes apply immediately. Auto-renaming on collision applies only when moving to another parent; a rename that collides with a sibling is rejected. Invalid parents and moves into self or a descendant are rejected. Do NOT use this for creating new folders (use create_folder) or updating reports (use update_report).
list_themes1 of 1 parameter describedUse this when the user wants to see the custom color themes defined for their account, which control the colors applied to Cloud Analytics reports. Returns a list of themes with their metadata. Do NOT use this for listing reports (use list_reports) or labels (use list_labels).
get_theme2 of 2 parameters describedUse this when the user wants to view details of a specific custom color theme. Accepts either the custom theme ID or a partial name (case-insensitive) across all custom themes. Multiple matches return an error listing names; id takes precedence. Preset themes cannot be fetched with this tool. Do NOT use this for listing all themes (use list_themes).
get_active_themeno parametersUse this when the user wants to know which color theme is currently active for the authenticated user (the theme applied to Cloud Analytics reports). Returns the active theme id; the reserved sentinel "default" means no custom or preset theme is selected and the built-in default is in use. Do NOT use this to list all themes (use list_themes) or to fetch a specific theme by id (use get_theme).
set_active_theme1 of 1 parameter describedUse this when the user wants to change the authenticated user’s active Cloud Analytics color theme. Accepts a custom theme ID or supported preset ID or the sentinel "default" to revert to the built-in default. Changes apply immediately. Requires Cloud Analytics edit permission. Create new themes with create_custom_theme. Do NOT use this to retrieve the current active theme (use get_active_theme) or to update theme colors (use update_theme).
update_theme5 of 5 parameters describedUse this when the user wants to modify an existing custom color theme — rename it, change its primary color, or update its color palette. Accepts either the theme ID or a partial name match across all custom themes; ambiguous matches return an error, and id takes precedence. Requires Cloud Analytics Admin; preset themes cannot be updated. Changes apply immediately to all users who have this theme active. Omitted fields are preserved; colors replaces both palettes. Create new themes with create_custom_theme; change the current user's active theme with set_active_theme.
get_aws_account1 of 1 parameter describedUse this when the user wants the CloudConnect details of a specific connected AWS account, such as its IAM role ARN, S3 bucket for real-time data, and which DoiT features are enabled or supported. Requires the 12-digit AWS account ID. Do NOT use this for Google Cloud or Azure accounts.
get_cloud_connect_supported_features1 of 1 parameter describedUse this when the user wants to know which DoiT CloudConnect features a connected AWS account supports and whether the account currently has the required permissions for each feature. Accepts a 12-digit AWS account ID, including AWS standalone accounts. Azure tenant IDs are unsupported. Returns the list of supported features with their permission status.
list_datahub_datasets1 of 1 parameter describedUse this when the user wants to see available DataHub datasets. Returns a list of datasets with metadata. Do NOT use this for billing data (use run_query) or assets (use list_assets).
get_datahub_dataset1 of 1 parameter describedUse this when the user wants to view details of a specific DataHub dataset by its name. Returns dataset metadata, including the schemaTemplate identifier when present, rather than the full column schema. Do NOT use this for listing all datasets (use list_datahub_datasets) or cost queries (use run_query).
create_datahub_dataset2 of 2 parameters describedUse this when the user wants to create a new DataHub dataset. Changes apply immediately. Do NOT use this for viewing datasets (use list_datahub_datasets) or sending events (use send_datahub_events).
update_datahub_dataset4 of 4 parameters describedUse this when the user wants to modify an existing DataHub dataset's description, displayName, or logoName. The dataset name identifies the dataset and cannot be changed. Omitted fields are kept; empty strings clear the supplied fields. At least one updatable field is required. Changes apply immediately. Do NOT use this for creating datasets (use create_datahub_dataset) or listing datasets (use list_datahub_datasets).
send_datahub_events1 of 1 parameter describedUse this when the user wants to send DataHub events for ingestion (1–50,000 events per call). Each event requires a provider name and an RFC 3339 timestamp, and can optionally include dimensions and metrics. The API validates the entire request atomically, including duplicate event IDs anywhere in the request; a validation failure rejects the whole request. Success means accepted for asynchronous processing, not that records are already queryable. No processing latency is guaranteed. Do NOT use this for creating datasets (use create_datahub_dataset) or viewing datasets (use list_datahub_datasets).
find_cloud_diagrams1 of 1 parameter describedUse this when the user wants to find architecture diagrams or cloud infrastructure diagrams. Matches cloud resource IDs (cld_id or props.id) and returns diagram viewer URLs and image URLs. Creates a sheet filter and queues image rendering. Do NOT use this for cost analysis (use run_query) or incidents (use get_cloud_incidents).
get_cloud_diagrams_stats3 of 3 parameters describedUse this when the user wants activity statistics for their cloud infrastructure diagrams over a time period — node create/update/delete change counts grouped by cloud service, plus each diagram's import/sync state. Useful for change auditing and drift detection. Requires a start and end RFC3339 date-time.
search_cloud_diagrams4 of 4 parameters describedUse this when the user wants to search their cloud infrastructure diagrams and components by name or property. Returns matching diagram layers (scheme), components, and components matched by property value (prop). ss_id scopes only component and prop results, not scheme results. from/size page each category independently. Do NOT use this for cost analysis (use run_query) or incidents (use get_cloud_incidents).
get_cloud_diagram_cost_snapshot4 of 4 parameters describedUse this when the user wants a cost snapshot for a specific cloud infrastructure diagram layer over a time period — the API-reported total, trendingPct as a percentage (25 means 25%, null when no prior value is available), the top five resources and top five services by cost, and the last twelve trend buckets. Both dates are inclusive. Requires the diagram layer ID and a startDate/endDate (YYYY-MM-DD). Do NOT use this for account-wide cost analysis (use run_query) or budgets (use list_budgets).
get_cloud_diagram_resource_relationships5 of 5 parameters describedUse this when the user wants to understand how a specific resource in a cloud infrastructure diagram is connected to other resources — its upstream/downstream edges and optional group membership (only when kind is group_members or both). Returns the anchor resource plus up to 200 relations with their type and hop distance; truncated is true when more than 200 relations exist. Requires the diagram layer ID and the resource ID. Do NOT use this for cost analysis (use get_cloud_diagram_cost_snapshot or run_query).
list_cloud_diagram_activity_groups5 of 5 parameters describedUse this when the user wants the activity history of a cloud diagram layer. Without tags, returns ALARM, COMMIT, EVENT, and SNAPSHOT activity groups for the given layer (ss_id), ordered by timestamp descending; snapshot groups reference a snapshot and contain their individual activity records. Supplying non-empty tags restricts results to snapshots. Page with offset/limit and filter with tags. Do NOT use this for cost analysis (use run_query) or incidents (use get_cloud_incidents).
list_cloud_diagram_node_activities5 of 5 parameters describedUse this when the user wants the change history of a single component node in a cloud diagram layer. Returns individual activity records (NODE_CREATE/NODE_UPDATE/NODE_DELETE) for the given node (ss_id + nodeId), ordered by timestamp descending, each including user as the ID of the user who made the change. Page with offset/limit. Do NOT use this for cost analysis (use run_query) or incidents (use get_cloud_incidents).
get_cloud_diagram_components5 of 5 parameters describedUse this when the user wants to discover all cloud infrastructure diagrams and their layers (statussheets), or to look up layer IDs needed for other diagram endpoints. With no filters, returns accessible application and infrastructure diagrams with layer metadata and no component data. Returns maps keyed by diagram and layer IDs. Selectors must belong to diagrams accessible to the authenticated customer and user. scheme_ids and the diagrams owning layer_ids are combined, not intersected. The layer IDs required by other diagram tools come from this tool. Optionally filter by diagram IDs (scheme_ids) or layer IDs (layer_ids), and set include_components=true to load projected component maps for up to five requested or resolved layers. Larger selections return an error before loading components; discover metadata first, then request batches of at most five layer_ids. Do NOT use this for cost analysis (use run_query) or diagram search (use search_cloud_diagrams).
list_budgets6 of 6 parameters describedUse this when the user wants to see their cloud spending budgets or check budget status. Returns a paginated list of budgets with names, amounts, and utilization. Do NOT use this for cost analysis (use run_query) or spending alerts (use list_alerts).
get_budget2 of 2 parameters describedUse this when the user wants to view the details and current utilization of a specific budget. Accepts either the budget ID or a partial name (case-insensitive). Do NOT use this for listing all budgets (use list_budgets) or cost analysis (use run_query).
create_budget19 of 19 parameters describedUse this when the user wants to create a new cloud budget with spending limits and alert thresholds. Requires name, currency, type, startPeriod, and exactly one of scope/scopes. Requires amount unless usePrevSpend is true, endPeriod for fixed budgets, and timeInterval for recurring budgets (ignored for fixed). Changes apply immediately. Do NOT use this for viewing existing budgets (use list_budgets or get_budget) or creating alerts (use create_alert).
update_budget20 of 20 parameters describedUse this when the user wants to modify an existing budget. Supports partial updates; omitted fields retain their current values. Setting type to fixed requires endPeriod; setting type to recurring requires timeInterval and forbids endPeriod; setting usePrevSpend to false requires amount. Changes apply immediately. Do NOT use this for viewing budgets (use list_budgets) or creating new budgets (use create_budget).
list_annotations5 of 5 parameters describedUse this when the user wants to see calendar annotations or notes on cost data. Returns a list of annotations. Do NOT use this for labels (use list_labels) or alerts (use list_alerts).
get_annotation2 of 2 parameters describedUse this when the user wants to view details of a specific annotation. Accepts either the annotation ID or a partial content match (case-insensitive) within the first 200 annotations. Multiple matches return an ambiguity error listing content; id takes precedence. Do NOT use this for listing all annotations (use list_annotations) or labels (use list_labels).
create_annotation4 of 4 parameters describedUse this when the user wants to add a new annotation to mark a specific date or event in cost data. Changes apply immediately. Do NOT use this for creating labels (use create_label) or alerts (use create_alert).
update_annotation5 of 5 parameters describedUse this when the user wants to modify an existing annotation. Nonempty content is required on every update. Omitted or null timestamp/reports/labels remain unchanged; reports and labels replace their lists, and [] clears them. Changes apply immediately. Do NOT use this for creating new annotations (use create_annotation) or labels (use update_label).
list_commitments5 of 5 parameters describedReturns a paginated list of spend commitment contracts from the DoiT Commitment Manager for Google Cloud, AWS, and Azure. These are negotiated spend commitments, rather than resource usage commitments; AWS agreements may be called Enterprise Discount Programs (EDP).
get_commitment1 of 1 parameter describedReturns details of a specific spend commitment contract for Google Cloud, AWS, or Azure, identified by its ID. Includes the full breakdown of commitment periods, per-period contracted values, and current spend attainment against the committed amount.
list_account_team1 of 1 parameter describedUse this when the user wants to know who their DoiT account team / account managers are. Returns the list of account managers assigned to the customer, including name, email, role, and Calendly scheduling link. Do NOT use this for listing platform users (use list_users) or organizations (use list_organizations).
get_resource_permissions2 of 2 parameters describedUse this when the user wants to see who a Cloud Analytics resource is shared with and at what access level. Returns the sharing settings (per-user roles and public visibility) for a specific alert, budget, report, or allocation. Requires resourceType (alerts, budgets, reports, or allocations) and resourceId. Do NOT use this to list the resources themselves (use list_alerts, list_budgets, list_reports, or list_allocations).
update_resource_permissions4 of 4 parameters describedUse this when the user wants to change who a Cloud Analytics resource is shared with or update access levels. Replaces sharing settings with PUT for a specific alert, budget, custom report, or allocation. Requires resourceType, resourceId and a nonempty permissions list with exactly one owner. Read current permissions first and retain all intended entries. Only the current owner or a user with Ownership assignment permission may transfer ownership. Omitted public makes reports, alerts and budgets private; allocations reject omitted/null public. Do NOT use this to view current permissions (use get_resource_permissions).
ask_ava_sync3 of 3 parameters describedAsk DoiT AVA, DoiT's AI assistant for cloud cost and infrastructure, a question about the user's DoiT account, cloud spending, anomalies, or optimization opportunities. AVA has access to the customer's billing data, usage patterns, and DoiT-specific features. It answers DoiT and cloud-specific questions, not general-purpose ones. Complex questions may take a long time. Timeouts and application error envelopes (including HTTP 200) return MCP errors.
confirm_action1 of 1 parameter describedRuns a generated DELETE operation that another tool staged and returned as `status: "approval_required"` with a summary and a one-time approval token. Intended for use after the user approves that summary. It runs exactly the saved request, including its customer scope, and returns that operation's own result or error. A token that is never confirmed expires after 5 minutes, and the staged action does not run. The token is bound to the authenticated caller and must match exactly; a different caller cannot run the action. A token runs at most once, even if execution fails. Creates and updates are not staged by the current tool registry.
create_signup_request5 of 7 parameters describedStart a Cloud Intelligence trial for an organization that is not yet a DoiT customer. These operations require no API key: they are rate limited, idempotent, and provision nothing until the organization's admin verifies the request. Agents create a request and hand the returned consentUrl to the admin; the admin verifies by entering the emailed code (or signing the request on the console), after which the tenant is provisioned and the request reports its customer id. Starts a Cloud Intelligence trial signup for the organization owning the email domain. Idempotent per Idempotency-Key: a retried create returns the same request. Nothing is provisioned until the admin verifies the request. Human channels (console, web) additionally require a Cloudflare Turnstile token and an accepted Terms of Service version; the emailed 6-digit verification code is then the consent act. Agents should present consentUrl to the organization's admin and poll getSignupRequest. Existing accounts, customer domains and previous trials receive the same pending response as new organizations. Eligibility is evaluated after mailbox verification or authenticated human consent.
get_signup_request2 of 3 parameters describedStart a Cloud Intelligence trial for an organization that is not yet a DoiT customer. These operations require no API key: they are rate limited, idempotent, and provision nothing until the organization's admin verifies the request. Agents create a request and hand the returned consentUrl to the admin; the admin verifies by entering the emailed code (or signing the request on the console), after which the tenant is provisioned and the request reports its customer id. Returns the current state of a signup request. Poll at the returned pollAfterSeconds cadence; once status is completed the response carries customerId, consoleUrl and signInUrl. The response never includes the requester's email or the verification code. A browser must send the Signup-Result-Token returned by verifySignupRequest to read results after email verification. Without it, the request remains pending until its consent window expires. Agents may read results after the matching authenticated human explicitly approves their request.
verify_signup_request2 of 3 parameters describedStart a Cloud Intelligence trial for an organization that is not yet a DoiT customer. These operations require no API key: they are rate limited, idempotent, and provision nothing until the organization's admin verifies the request. Agents create a request and hand the returned consentUrl to the admin; the admin verifies by entering the emailed code (or signing the request on the console), after which the tenant is provisioned and the request reports its customer id. Confirms ownership of the admin email by entering the 6-digit code that was emailed when the request was created (or resent). Success records consent and starts provisioning; the request moves to consented and then completed. Five wrong codes lock the current code; request a new one with resendSignupVerification.
create_signup_session2 of 3 parameters describedStart a Cloud Intelligence trial for an organization that is not yet a DoiT customer. These operations require no API key: they are rate limited, idempotent, and provision nothing until the organization's admin verifies the request. Agents create a request and hand the returned consentUrl to the admin; the admin verifies by entering the emailed code (or signing the request on the console), after which the tenant is provisioned and the request reports its customer id. Exchanges the one-time activationToken returned by verifySignupRequest for a Firebase custom token once the request is completed, so the browser that entered the code lands in the new tenant without a second email. The token is bound to the request, single-use and valid for 10 minutes. Sign in with signInWithCustomToken against tenantId, then open consoleUrl.
resend_signup_verification1 of 2 parameters describedStart a Cloud Intelligence trial for an organization that is not yet a DoiT customer. These operations require no API key: they are rate limited, idempotent, and provision nothing until the organization's admin verifies the request. Agents create a request and hand the returned consentUrl to the admin; the admin verifies by entering the emailed code (or signing the request on the console), after which the tenant is provisioned and the request reports its customer id. Emails a fresh 6-digit code to the requester. At most three codes per request, at least 60 seconds apart.
list_alert_slack_channels2 of 4 parameters describedNotifications triggered when cloud costs exceed defined thresholds or meet specific conditions. Lists Slack destinations eligible for Alert notifications for the authenticated customer and caller. Returns canonical identifiers for recipientsSlackChannels and integration status. User credentials include visible private channels; service accounts return public/shared channels only. Results are sorted by stable destination identity. Keep nameContains unchanged when following pageToken. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
delete_alert1 of 2 parameters describedNotifications triggered when cloud costs exceed defined thresholds or meet specific conditions. Deletes the alert specified by the Id. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_allocation1 of 2 parameters describedDefine how costs are distributed across your organization. Deletes the allocation specified by the Id. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_annotation1 of 2 parameters describedCustom notes added to cost data to provide contextual information. Deletes the annotation specified by the Id. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_label1 of 2 parameters describedCreate and manage labels to organize and categorize your cloud resources. Deletes the label specified by the Id. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
create_custom_theme4 of 4 parameters describedConfigure presentation settings for Cloud Analytics reports, including custom color themes. Creates a new custom color theme. Requires Cloud Analytics Admin permission.
delete_custom_theme1 of 2 parameters describedConfigure presentation settings for Cloud Analytics reports, including custom color themes. Deletes the custom theme specified by the Id. Requires Cloud Analytics Admin permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_budget1 of 2 parameters describedTrack actual cloud spend against planned spend. Deletes the specified budget. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
list_budget_suggestions2 of 2 parameters describedAI-generated budget recommendations you can accept (link to a budget you created) or dismiss. Returns the pending AI-generated budget suggestions for your account. The set is small (a handful of pending suggestions) and is returned in full. Each suggestion can be accepted (after you create a matching budget via `POST /analytics/v1/budgets`) or dismissed.
accept_budget_suggestion3 of 4 parameters describedAI-generated budget recommendations you can accept (link to a budget you created) or dismiss. Marks the suggestion as accepted and links it to an existing budget. Create the budget first via `POST /analytics/v1/budgets`, then pass its `id` as `budgetId`. The budget must belong to your account.
dismiss_budget_suggestion1 of 3 parameters describedAI-generated budget recommendations you can accept (link to a budget you created) or dismiss. Marks the suggestion as dismissed so it no longer appears in the pending list.
delete_folder1 of 2 parameters describedOrganize Cloud Analytics resources (reports, allocations) into folders. Deletes the specified folder. All nested folders will be deleted. Any reports or allocations contained in the folder are moved to the root. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_report1 of 2 parameters describedManage Cloud Analytics reports and get reports data in JSON format. Deletes the specified Cloud Analytics report. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
async_run_inline2 of 4 parameters describedManage Cloud Analytics reports and get reports data in JSON format. Submits an async report execution job using an inline configuration. Returns 202 immediately with a Location header pointing to the operation status endpoint. Requires the Idempotency-Key header to ensure at-most-once submission. Duplicate requests with the same config for the same customer return the existing in-flight operation. Use ?dryRun=true to validate the config without creating an operation.
get_async_operation1 of 2 parameters describedManage Cloud Analytics reports and get reports data in JSON format. Returns the current status of an async report operation. Non-terminal operations (pending, running) include a Retry-After header suggesting when to poll again. This endpoint does not return result data — once status is "succeeded", fetch the result from the operation's results endpoint. When status is "failed", the error field contains an RFC 9457-shaped error. Returns 404 if the operationId does not exist, belongs to a different tenant, or has expired.
async_run_report_by_id1 of 7 parameters describedManage Cloud Analytics reports and get reports data in JSON format. Submits an async execution job for a saved report identified by ID. Returns 202 immediately with a Location header pointing to the operation status endpoint. Requires the Idempotency-Key header. Use ?dryRun=true to validate without creating an operation.
cancel_async_operation1 of 4 parameters describedManage Cloud Analytics reports and get reports data in JSON format. Cancels a pending or running async report operation. Already-terminal operations (succeeded, failed, canceled) are returned as-is without any state change (idempotent). Returns 404 if the operationId does not exist or belongs to a different tenant. Use ?dryRun=true to validate the request without modifying any state.
get_async_operation_results1 of 3 parameters describedManage Cloud Analytics reports and get reports data in JSON format. Returns the result of a succeeded async report operation, including report metadata (id, reportName, owner, type, createTime, updateTime, urlUI) when the operation was started against a saved report — the same shape as the sync GetReportResponse, instead of requiring a second call to GET /analytics/v1/reports/{id}/config for it. Returns 404 if the operationId does not exist, has expired, or belongs to a different tenant. Returns 425 Too Early if the operation has not yet reached a terminal state — poll the operation status endpoint, which returns its own Retry-After guidance, until it succeeds. Returns 422 if the operation terminated as failed or canceled. Returns 413 if the result is too large to return inline — request it again with `fileOutput=json`, or narrow the report. The poll status endpoint response does not include result data inline — this is the only endpoint that returns it.
list_widgets2 of 3 parameters describedBeta. Read precomputed current-month cloud spend and forecast metrics. Widget results are refreshed in the background; reading a widget returns the latest cached result and never starts a synchronous refresh. Use the list operation to discover the complete catalogue. Returns the complete catalogue of preset widgets supported by the Analytics Widgets API. Each entry contains a customer-specific `id` and a stable customer-facing `alias`; either value can be passed to the get-widget operation. An `id` can vary by customer or service tier, while an `alias` remains stable. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on multiple customers, send `X-Tenant-Id: <tenant-id>` to select the customer. A `403` response means the caller or selected customer is not authorized or entitled to use this API.
get_widget1 of 3 parameters describedBeta. Read precomputed current-month cloud spend and forecast metrics. Widget results are refreshed in the background; reading a widget returns the latest cached result and never starts a synchronous refresh. Use the list operation to discover the complete catalogue. Returns the latest precomputed cached result for one widget. This read does not refresh or recompute the widget synchronously. Use either the customer-specific `id` returned by the list-widgets operation or one of these stable aliases: - `current-month-cloud-spend` — total cloud spend accumulated during the current calendar month. - `current-month-cloud-forecast` — forecast of total cloud spend for the current calendar month. The two concrete alias requests are: - `GET https://api.doit.com/analytics/v1/widgets/current-month-cloud-spend` - `GET https://api.doit.com/analytics/v1/widgets/current-month-cloud-forecast` Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on multiple customers, send `X-Tenant-Id: <tenant-id>` to select the customer. A `403` response means the caller or selected customer is not authorized or entitled to use this API. The result's `period.endTime` is exclusive. Monetary `amount` values are decimal strings and `currency` values are ISO 4217 currency codes. `monthToMonthGrowthPercentage` and `monthToMonthGrowthAmount` are both `null` when no comparable prior-period value exists.
list_contracts2 of 3 parameters describedList and manage tenant-scoped contracts as a T1/T2 PartnerOps caller. Lists the contracts held by the specified customer. Callable by a T1/T2 PartnerOps principal for its own tenant or any descendant tenant. Read access requires the contractsViewer or contractsManager permission, plus the billing:contracts or channelops entitlement. User API tokens must include one of the permissions in their scope.
get_contract1 of 3 parameters describedList and manage tenant-scoped contracts as a T1/T2 PartnerOps caller. Returns the specified contract. Requires the contractsViewer or contractsManager permission. User API tokens must include one of them in their scope.
patch_anomaly2 of 3 parameters describedMonitor cost spikes in your cloud environment. Updates the review status of the anomaly identified by `{id}`, the same identifier `getAnomaly` accepts. Mirrors the review workflow available in the console: set `reviewStatus`, and when resolving, qualify it with `resolution` and optionally a `resolutionNote` (feedback reason and comment). The change is recorded in the anomaly's review history exactly like a console update, and the actor is derived from the API credentials - never from the request body. Validation: `reviewStatus` is one of `NEEDS_REVIEW`, `UNDER_REVIEW`, `RESOLVED`; `resolution` (`ANOMALY_CONFIRMED` or `NOT_ANOMALY`) is required when `reviewStatus` is `RESOLVED` and forbidden otherwise; `resolutionNote.reason` must belong to the given `resolution` - `SECURITY_BREACH`, `MISCONFIGURATION`, `UNINTENTIONAL_PROVISIONING`, `EXPECTED_COST_SPIKE` or `ANOMALOUS_OTHER` for `ANOMALY_CONFIRMED`, and `FAULTY_ANOMALY_DETECTION_MODEL`, `INCORRECT_DATA`, `LOW_IMPACT` or `NON_ANOMALOUS_OTHER` for `NOT_ANOMALY`. Requires the `AnomaliesManager` permission and the `governance:costAnomalies` and `governance:costAnomalies:acknowledgement` entitlements.
get_anomaly_explanation1 of 2 parameters describedMonitor cost spikes in your cloud environment. Returns a likely-cause explanation for the specified anomaly, alongside the deterministic facts and evidence references it was generated from. The explanation itself is AI-generated; it is always returned separately from the deterministic `facts`, and is marked as such in the `explanation` object. Generation is ephemeral: no conversation is persisted on your behalf. Requires the `governance:costAnomalies` entitlement and the `AnomaliesViewer` permission.
create_asset1 of 5 parameters describedManage cloud resources or services in your cloud environment. Creates a new asset.
datahub_events_csv_file7 of 7 parameters describedIngest third-party cost, usage, and metric-based data for analysis. Sends a batch of events to DataHub using a CSV file, either uncompressed or compressed in ZIP or GZ format. It may take up to 15 minutes for the data to become available in the DoiT console.
datahub_import_provider_records5 of 7 parameters describedIngest third-party cost, usage, and metric-based data for analysis. Sends provider-native records as JSON instead of a CSV file. The records use the same columns as the template's CSV (currently `anthropic-spend-report@1` only) and are validated, normalized and booked on `periodEnd` exactly like a CSV upload. It may take up to 15 minutes for the data to become available in the DoiT console.
delete_datahub_events_by_filter4 of 5 parameters describedIngest third-party cost, usage, and metric-based data for analysis. Deletes specific events using filters. Note that the two filters, `eventIds` and `time ranges`, are mutually exclusive.
delete_datahub_datasets2 of 2 parameters describedIngest third-party cost, usage, and metric-based data for analysis. Deletes one or more DataHub datasets and all their associated data. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_datahub_dataset1 of 2 parameters describedIngest third-party cost, usage, and metric-based data for analysis. Deletes a specific DataHub dataset. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
export_datahub_dataset_records1 of 7 parameters describedIngest third-party cost, usage, and metric-based data for analysis. Returns one page of the live records of a DataHub dataset, as CSV (default) or as newline-delimited JSON in the same shape as the `/datahub/v1/events` payload. A time window is required: `startTime` is inclusive, `endTime` is exclusive, and the window must not exceed 366 days. Rows are ordered by their event time and event id, and pages never overlap: read the `X-Next-Page-Token` response header and pass it back as `pageToken` until the header is absent. `X-Row-Count` carries the number of rows in the page. Only live rows are returned; rows deleted through the console or the delete endpoints are excluded. Every row starts with five provenance columns (`event_id`, `batch`, `source`, `export_time`, `updated_by`) followed by the dataset's business columns in the CSV ingest vocabulary (`usage_date`, `fixed.<key>`, `label.<key>`, `project_label.<key>`, `system_label.<key>`, `metric.<type>`). The business columns are computed from the rows of each page, so consecutive pages can have different label and metric columns; union the headers when concatenating pages. Datasets created with the FOCUS schema template use the FOCUS column names instead and can only be exported as CSV. To re-import an export into another dataset, drop the `batch`, `source`, `export_time` and `updated_by` columns, and either drop `event_id` or rename it to `id`. This tool returns a JSON envelope with data (the unchanged CSV or JSONL page body) and pageToken (from X-Next-Page-Token). Pass a non-empty pageToken back as pageToken to advance; null means the final page. MCP does not expose the HTTP headers directly.
get_invoice_pdf1 of 2 parameters describedAccess your current and historical billing documents. Returns the PDF document for the invoice specified by the invoice number, including a cancelled invoice or credit memo. The response body is the PDF bytes. The PDF is returned decompressed by default. It is only gzip-compressed when the request advertises `Accept-Encoding: gzip`, in which case the response carries `Content-Encoding: gzip` with a `Content-Length` for the compressed bytes and must be decoded as a standard `Content-Encoding: gzip` body. HTTP clients whose stack negotiates the encoding automatically also decode it automatically; a client that sets the header by hand may instead receive the raw gzip bytes (for example `curl` decodes only with `--compressed`). Omit `Accept-Encoding` (or send `identity`) to always receive the decompressed PDF. A very large invoice may exceed the decompressed-response size limit and respond with `500`; request it with `Accept-Encoding: gzip` to stream the compressed bytes without that limit. A `404` is returned both when no invoice with the given number exists for the authenticated tenant and when the invoice exists but has no PDF document available.
get_billing_explainer_per_payer1 of 3 parameters describedExplain month-over-month changes in invoiced cloud costs. Returns the invoiced cost changes for each payer in the authenticated tenant.
get_entity_invoice_explainer1 of 4 parameters describedExplain month-over-month changes in invoiced cloud costs. Returns invoiced cost changes for an invoice owned by the specified billing profile in the authenticated tenant.
list_service_quotas1 of 5 parameters describedMonitor cloud service quota usage across connected accounts and projects. Returns the latest service quota usage snapshots collected by DoiT for the authenticated customer. Results include only quotas retained by DoiT's monitoring collectors and are not a complete or live inventory from the cloud providers. Results are sorted by utilization percentage in descending order. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_contract_templates2 of 2 parameters describedManage contract templates for PartnerOps resellers (T1/T2). Lists contract templates owned by the authenticated tenant (from the bearer token). Requires ContractTemplatesAdmin and the `channelops:contracts:templates` entitlement.
get_contract_template1 of 2 parameters describedManage contract templates for PartnerOps resellers (T1/T2). Returns a single contract template owned by the authenticated tenant (from the bearer token). Requires ContractTemplatesAdmin and the `channelops:contracts:templates` entitlement.
assign_contract_template2 of 3 parameters describedManage contract templates for PartnerOps resellers (T1/T2). Applies a contract template owned by the authenticated tenant (from the bearer token) to child customers, creating a draft contract for each. Drafts have no billing effect until each one is completed and activated. The template must not be archived, and the current date must fall within its eligibility window. Requires ContractTemplatesAdmin and the `channelops:contracts:templates` entitlement.
list_customer_notifications2 of 2 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Returns every organization notification config for the tenant as an unpaginated `{ "items": [...] }` array. Items are ordered by `createTime` ascending, then by `id` ascending. Only configs whose settings use the public types on `CustomerNotificationSettings` are returned. Dashboard, report, and commitment subscriptions are separate documents and are omitted. A prompt schedule is personal and is omitted. Creating one of those in the Console does not change a config created with this API. Requires the `settings` (Manage settings) permission. The API does not offer the Console's read-only Organization list; a caller without this permission receives `403`.
create_customer_notification4 of 6 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Creates an organization-wide notification config. `settings` names one or more public types. Destinations are `emails`, `slackChannels`, and `teamsChannels` arrays. The response returns those three arrays. A channel that a subscribed type does not support is `422` `customers.channel_not_supported`. A Teams destination on a type that supports Teams is `422` `validation_failed` when the tenant has no Teams entitlement. Requires the `settings` (Manage settings) permission. The `Idempotency-Key` header is required. The same key and the same body replay the stored success. A different body is `422` `idempotency_key_reused`. A `5xx` response may leave the key reserved, so a retry returns `409` until the original request is released or about 30 minutes pass. `dryRun=true` does not reserve the key. With `dryRun=true` the request goes through the same checks as a real create and returns `200` with `X-Dry-Run: true` and null identity fields (`id`, `createTime`, `updateTime`, `etag`) without creating anything. Reads are immediately consistent. After a `201`, a GET of that notification returns the created config.
get_customer_notification1 of 2 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Returns one public organization notification config. Requires the `settings` (Manage settings) permission. The API does not offer the Console's read-only Organization list; a caller without this permission receives `403`. An id whose config stores a dashboard, report, or commitment subscription or a prompt schedule, or that is not a config for this tenant, returns `404`, without saying whether it exists elsewhere. PATCH and DELETE of that id also return `404` and leave the stored document unchanged.
delete_customer_notification1 of 5 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Permanently deletes a public organization notification config. A visible config holds only public types, so the whole document is removed. Requires the `settings` (Manage settings) permission and the `If-Match` header. The `Idempotency-Key` header is required. The same key, the same body, and the same `If-Match` replay the stored success. A different body or a different `If-Match` is `422` `idempotency_key_reused`. A `5xx` response may leave the key reserved, so a retry returns `409` until the original request is released or about 30 minutes pass. `dryRun=true` does not reserve the key. With `dryRun=true` the request goes through the same checks as a real delete without deleting anything. Deleting an id whose config stores a dashboard, report, or commitment subscription or a prompt schedule, or that no longer exists, returns `404`. Reads are immediately consistent. After a completed delete (`204` without `X-Dry-Run: true`), a GET of that notification returns `404`. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_customer_notification4 of 8 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Partially updates an organization notification with an `application/merge-patch+json` body (RFC 7396). Omitted fields stay unchanged; nested objects are deep-merged; nested arrays (for example `allocations.ids`) are replaced when present. When `destinations` is present it replaces the whole destinations object; the nested `emails`, `slackChannels`, and `teamsChannels` arrays are the full lists. Send `null` for a settings property to unsubscribe that type. Nulling the last type is `422`. A channel that a remaining type does not support is `422` `customers.channel_not_supported`. A Teams destination on a type that supports Teams is `422` `validation_failed` when the tenant has no Teams entitlement. Optional resend fields are cleared with `null` (for example `"settings":{"costAnomalies":{"repeat":null}}`). `minSeverity`, `minExcessCost`, and `allocations` cannot be cleared. An id whose config stores a dashboard, report, or commitment subscription or a prompt schedule returns `404`. A settings property that is not on `PatchCustomerNotificationSettings` is `422`. Requires the `settings` (Manage settings) permission and the `If-Match` header. The `Idempotency-Key` header is required. The same key, the same body, and the same `If-Match` replay the stored success. A different body or a different `If-Match` is `422` `idempotency_key_reused`. A `5xx` response may leave the key reserved, so a retry returns `409` until the original request is released or about 30 minutes pass. `dryRun=true` does not reserve the key. With `dryRun=true` the request goes through the same checks as a real update and returns the notification as it would look after the patch, without changing anything. Reads are immediately consistent. After a completed update, a GET of that notification returns the new state.
get_customer1 of 2 parameters describedRead and update your organization's general settings. Returns the customer, including its general settings and contact info, scoped to `{customerId}`. `{customerId}` must match the customer resolved from the bearer token; a token scoped to a different customer gets `403`, even if that customer would otherwise be reachable through a reseller/MTS relationship. Requires the `Settings` permission.
update_customer4 of 5 parameters describedRead and update your organization's general settings. Partially updates the general settings and contact info of the customer identified by `{customerId}`. `{customerId}` must match the customer resolved from the bearer token; a token scoped to a different customer gets `403`, even if that customer would otherwise be reachable through a reseller/MTS relationship. Requires the `Settings` permission; updating `allowedInviteDomains` additionally requires the `UsersManager` permission. The request body must use `application/merge-patch+json` (RFC 7396): an omitted field leaves the current value unchanged, and an explicit `null` also leaves it unchanged, except for `urlSlug`, where an explicit empty string removes the customer's active URL slug rather than leaving it unchanged. Fields are nested exactly as `getCustomer` returns them - `currency` and `allowedInviteDomains` under `settings`, `emails` under `contact` - so every value is read and written at the same path. `settings.currency` accepts only the codes listed in the schema and cannot be cleared; `allowedInviteDomains` and `contact.emails` are cleared with an empty array.
list_shared_payer_account_mappings2 of 4 parameters describedLink and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Lists the AWS accounts under the reseller's linked shared payers, together with the end customer each is currently mapped to. `{customerId}` (the reseller itself) means the account has not yet been reassigned to an end customer. Each payer's own management account is included alongside its member accounts. Requires the `SharedPayersAdmin` permission and the AWS integration (`pdi:aws`) entitlement. User API tokens must include the permission in their scope.
list_shared_payer_management_accounts2 of 3 parameters describedLink and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Lists the reseller's linked shared-payer management (payer) accounts that have completed onboarding, for use in an account picker. Requires the `SharedPayersAdmin` permission and the AWS integration (`pdi:aws`) entitlement. User API tokens must include the permission in their scope.
list_shared_payers2 of 3 parameters describedLink and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Lists every shared payer linked to the reseller, including ones still mid-onboarding, with per-payer counts of linked and mapped accounts. Requires the `SharedPayersAdmin` permission and the AWS integration (`pdi:aws`) entitlement. User API tokens must include the permission in their scope.
reassign_shared_payer_account2 of 3 parameters describedLink and manage shared-payer account mappings for PartnerOps resellers (T2), reassigning AWS accounts under a shared payer to T3 end customers. Reassigns one AWS account under a linked shared payer - a member account or the payer's own management account - to the reseller itself or to a T3 end customer within its hierarchy. Requires the `SharedPayersAdmin` permission and the AWS integration (`pdi:aws`) entitlement. User API tokens must include the permission in their scope.
list_customer_subscriptions1 of 3 parameters describedCreate, view, update, and delete dashboard, report, commitment, alert, and budget subscriptions. This is not Organization-wide notifications. Lists dashboard, report, commitment, alert, and budget subscriptions visible to the caller. Items are ordered by `id` ascending. Nested `subscriptions` are ordered by `type` ascending. `maxResults` defaults to 50. An omitted value, `0`, or a value above 500 is treated as 50. A non-integer `maxResults` is `400`. Pass the response `pageToken` to request the next page. That field is absent when there are no more pages. A `pageToken` that matches no id is `400`. `rowCount` is the total number of subscriptions visible to the caller. That value is the same on every page. One subscription record is one item. Its dashboard, report, and commitment subscriptions are nested entries that share `recipients`. An alert is one item. A budget is one item. An alert or a budget never shares an item with a scheduled subscription. Draft budgets are omitted. An alert is included only when the tenant has the Governance Alerts entitlement and the caller can view that alert. When the entitlement is missing or cannot be confirmed, the list contains no alerts. An alert with no recipients is still included. One id namespace is shared by a scheduled subscription, an alert, and a budget. Create accepts only `dashboard-subscription`, `report-subscription`, and `commitment-manager`. Those scheduled types are the resource: create, recipient replace, subscription-set replace, and delete. GET returns alerts and budgets so a caller can see who receives them. Create, delete, and full management of those resources, including recipients, stay on `PATCH /analytics/v1/alerts/{id}` and `PATCH /analytics/v1/budgets/{id}`. PATCH on this API may replace those same recipient lists. DELETE of an alert or a budget returns `409` `customers.entry_is_resource`. Manage Settings users can view every subscription. A scheduled subscription is also visible to its creator when the caller has the permission for that type, to an owner, editor, or viewer of its source, and to one of its email recipients. Users Manager alone grants no access. A service-account token is evaluated from its own permissions and does not inherit the permissions of the subscription creator. A caller who can see only some nested subscriptions still receives that record; `subscriptions` omits the entries they cannot see. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
create_customer_subscription3 of 5 parameters describedCreate, view, update, and delete dashboard, report, commitment, alert, and budget subscriptions. This is not Organization-wide notifications. Creates one dashboard, report, or commitment subscription with one, two, or three scheduled subscriptions: `dashboard-subscription`, `report-subscription`, and `commitment-manager`. Create does not accept `alert` or `budget`. Each type appears at most once. The response is that subscription. Nested entries are ordered by `type`. `name` is `{source name} (Dashboard Subscription)`, `(Report Subscription)`, or `(Commitment Subscription)`, taken from the nested type that sorts first. `createdBy` is the caller. `subscriptions` must contain one to three entries. A repeated type is `422` `customers.duplicate_subscription_type`. An `alert` or `budget` type, an empty `subscriptions` array, or any server-set field (`id`, `name`, `createdBy`, `etag`, `permissions`, `source.name`, `schedule.nextAt`) is `422` `validation_failed`. `source.id` must belong to the tenant. A missing or foreign source is `422` `validation_failed`. Recipient and schedule value rules are on `CustomerSubscriptionRecipients` and `CustomerSubscriptionScheduleInput`. The caller must be allowed to manage every sent type: a DoiT employee, Manage Settings, or the permission for that type. Users Manager alone grants no access. `Idempotency-Key` is required. The same key, caller, customer, method, path, and body replays the stored success response. A different body for that key is `422` `idempotency_key_reused`. A missing key is `400` `idempotency_key_required`. While the first request is in progress, another request with that key is `409` `idempotency_request_in_progress`. A `4xx` response releases the key. `dryRun=true` does not reserve the key. It returns the would-be subscription with `id` and `etag` null and writes nothing. Reads are immediately consistent. After a `201`, a GET of that id returns the created subscription. The first delivery can take up to an hour.
get_customer_subscription1 of 2 parameters describedCreate, view, update, and delete dashboard, report, commitment, alert, and budget subscriptions. This is not Organization-wide notifications. Returns one dashboard, report, commitment, alert, or budget subscription. The body is the same object as a list item. `schedule` is omitted on an alert or a budget. Create does not accept `alert` or `budget`. GET returns them. PATCH may replace their recipient lists, which writes the same lists as `PATCH /analytics/v1/alerts/{id}` and `PATCH /analytics/v1/budgets/{id}`. Create, delete, and full management stay on those APIs. DELETE of an alert or a budget returns `409` `customers.entry_is_resource`. Manage Settings users can view the subscription. A scheduled subscription is also visible to its creator when the caller has the permission for that type, to an owner, editor, or viewer of its source, and to one of its email recipients. Users Manager alone grants no access. A service-account token is evaluated from its own permissions and does not inherit the permissions of the subscription creator. Keys the caller cannot see are omitted from `subscriptions`. A missing, foreign-tenant, or non-visible subscription returns `404` without revealing whether it exists.
delete_customer_subscription1 of 5 parameters describedCreate, view, update, and delete dashboard, report, commitment, alert, and budget subscriptions. This is not Organization-wide notifications. Deletes a dashboard, report, or commitment subscription and every scheduled entry on it. Returns `204`. Deleting an id that is already gone also returns `204`, so a retry does not fail. `If-Match` is required when the document still exists; a stale value is `412`. An id that matches no scheduled subscription, alert, or budget returns `204` when `If-Match` is present. Create does not accept `alert` or `budget`. GET returns them. PATCH may replace their recipient lists. DELETE of an alert or a budget returns `409` `customers.entry_is_resource`. The caller must have `canDelete` for the subscription. Manage Settings users, a creator with the permission for each scheduled type, and a source owner or editor may delete it. Source viewers and recipients cannot. Users Manager alone grants no access. A service-account token is evaluated from its own permissions and does not inherit the permissions of the subscription creator. `Idempotency-Key` is required. The same key, caller, customer, method, path, and `If-Match` replays the stored success response. A different `If-Match` is `422` `idempotency_key_reused`. A missing key is `400` `idempotency_key_required`. While the first request is in progress, another request with that key is `409` `idempotency_request_in_progress`. A `4xx` response releases the key. `dryRun=true` does not reserve the key and does not delete. Reads are immediately consistent. After a completed delete, a GET of that id returns `404`. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_customer_subscription3 of 7 parameters describedCreate, view, update, and delete dashboard, report, commitment, alert, and budget subscriptions. This is not Organization-wide notifications. Partially updates one dashboard, report, commitment, alert, or budget subscription with an `application/merge-patch+json` body (RFC 7396). The writable fields are `recipients.emails`, `recipients.slackChannels`, and, on a scheduled subscription, `subscriptions`. Any other field, `recipients: null`, or `null` for either recipient list is `422` `validation_failed`. A patch that sets neither `recipients` nor `subscriptions` is `422` `validation_failed`. A wrong `Content-Type` is `415`. Recipient and schedule value rules are on `CustomerSubscriptionRecipients`, `CustomerSubscriptionRecipientPatch`, and `CustomerSubscriptionScheduleInput`. On a scheduled subscription, `subscriptions` is the desired set of dashboard, report, and commitment subscriptions. A type in the body and not on the document is added. A type on the document and missing from the body is removed. A type in both is updated when `source.id` or the schedule differs, and `nextAt` is recalculated. A stored entry this API does not list stays on the subscription. An empty `subscriptions` array is `422` `validation_failed`; deleting the item is `DELETE`. A repeated type is `422` `customers.duplicate_subscription_type`. An omitted `subscriptions` array leaves the nested types unchanged. Create does not accept `alert` or `budget`. GET returns them. On an alert or a budget, `subscriptions` is accepted only when it is the one stored entry with the same `type` and `source.id` and no `schedule`. Any other array is `422` `validation_failed`. Those items never gain a dashboard, report, or commitment subscription. Alerts and budgets keep their own APIs for create, delete, and full management. This `PATCH` is the one write this API makes on them, and it may replace their recipient lists. DELETE of an alert or a budget returns `409` `customers.entry_is_resource`. A patch whose normalized values match the stored values returns `200` and does not write. The `etag` is unchanged. Recipient changes are allowed when the caller can edit every key on the document, including a key the response did not show. Otherwise they are allowed only when the caller removes exactly their own email: no added address, no Slack change, and no subscription-set change. Any other recipient change is `403`. The caller must be allowed to manage every added or changed scheduled type and to delete every removed type. `If-Match` must contain the current strong ETag. The token only covers fields this API can write. `Idempotency-Key` is required. The same key, caller, customer, method, path, body, and `If-Match` replays the stored success response. A different body or `If-Match` is `422` `idempotency_key_reused`. A missing key is `400` `idempotency_key_required`. While the first request is in progress, another request with that key is `409` `idempotency_request_in_progress`. A `4xx` response releases the key. `dryRun=true` does not reserve the key. It returns the would-be subscription with the current `etag` and writes nothing. Reads are immediately consistent. After a completed update, a GET of that id returns the new state.
delete_user1 of 2 parameters describedManage users who have access to the DoiT platform. Deletes a user. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
resend_invite1 of 4 parameters describedManage users who have access to the DoiT platform. Resets the invite expiry to 48 hours from now, invalidates the previous invite token (so old email links stop working), and triggers a fresh invitation email. Works on invites in any state including `Cancelled` — resending a cancelled invite reactivates it to `Pending`. Returns `404` if no invite exists for the given ID (never created, or already accepted and removed). Requires `usersManager` permission.
cancel_invite1 of 4 parameters describedManage users who have access to the DoiT platform. Marks the invite as `Cancelled` and invalidates the invite token so any outstanding email links stop working. The invite document is retained (soft cancel) — the user row remains visible in `GET /iam/v1/users` with `inviteStatus: Cancelled`. Use `DELETE /iam/v1/users/{id}` to fully remove the record. Returns `404` if no invite exists for the given ID, and `409` if the invite is already cancelled. Requires `usersManager` permission.
list_user_notifications2 of 3 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Returns every personal notification config for the user as an unpaginated `{ "items": [...] }` array. One user has a handful of configs; there is no pagination. Items are ordered by `createTime` ascending, then by `id` ascending. Requires Users Manager (`usersManager`). The user id must belong to the resolved tenant.
create_user_notification3 of 6 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Creates a personal notification config for the user. The request body has no email address; the server copies the target user's email onto the config as the sole destination. `settings` has one property per subscribed type and must include at least one. `costAnomalies` is optional. Requires Users Manager (`usersManager`). The user id must belong to the resolved tenant. For each subscribed type other than `costAnomalies`, the target user must also hold that type's permission. The permission id for each type is documented on `UserNotificationSettings`. If they do not, the response is `403` and the problem body includes `permission` (the permission id) and `notificationType` (the settings property). A permission lookup that fails is `503`. If the permission service does not recognize an invited user, the response is `403`. Requires the `Idempotency-Key` header so a retried create with the same key and body returns the original response and does not create a second config. With `dryRun=true` the request goes through the same checks as a real create and returns `200` with `X-Dry-Run: true` and null identity fields (`id`, `createTime`, `updateTime`, `etag`) without creating anything. Reads are immediately consistent. After a `201`, a GET of that notification returns the created config.
get_user_notification1 of 3 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Returns one personal notification config. Requires Users Manager (`usersManager`). A subscribed type stays in the response when the target user later loses that type's permission; the type permission is not re-checked on read. A notification id that does not belong to this user in the resolved tenant returns `404`, without saying whether it exists elsewhere.
delete_user_notification1 of 6 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Permanently deletes a personal notification config. Requires Users Manager (`usersManager`), the `If-Match` header, and the `Idempotency-Key` header. With `dryRun=true` the request goes through the same checks as a real delete without deleting anything. Deleting an id that no longer exists returns `404`. Reads are immediately consistent. After a completed delete (`204` without `X-Dry-Run: true`), a GET of that notification returns `404`. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_user_notification3 of 8 parameters describedPersonal notification configs for a user, and organization-wide cost anomaly notifications. Partially updates a personal notification with an `application/merge-patch+json` body (RFC 7396). Omitted fields stay unchanged; nested objects are deep-merged; nested arrays (for example `allocations.ids`) are replaced when present. Optional resend fields are cleared with `null` (for example `"settings":{"costAnomalies":{"repeat":null}}`). Send `null` for a settings property to unsubscribe that type. Nulling the last remaining type is `422`, decided before the type-permission check, so the status does not depend on which permissions the target user holds. Requires Users Manager (`usersManager`). For each type still subscribed after the merge, other than `costAnomalies`, the target user must hold that type's permission, including when the patch does not mention that type (a rename included). The permission id for each type is documented on `UserNotificationSettings`. A missing permission is `403` with `permission` and `notificationType`. A permission lookup that fails is `503`. The request also requires the `If-Match` header and the `Idempotency-Key` header. With `dryRun=true` the request goes through the same checks as a real update and returns the notification as it would look after the patch, without changing anything. Reads are immediately consistent. After a completed update, a GET of that notification returns the new state.
create_role4 of 5 parameters describedManage user permissions and access levels in your organization. Creates a custom role in the authenticated customer with the given permission IDs. Permission IDs are the `permissions` values returned by `GET /iam/v1/roles`. A service account of a parent tenant can create the role in a descendant tenant by setting `X-Tenant-Id` to that tenant's customer ID. Requires the `Idempotency-Key` header so a retried request does not create a second role.
get_role1 of 2 parameters describedManage user permissions and access levels in your organization. Returns a single role by ID. Preset roles are visible to every customer; a custom role is returned only to the customer that owns it. A service account of a parent tenant can read a descendant tenant's role by setting `X-Tenant-Id` to that tenant's customer ID.
delete_role1 of 2 parameters describedManage user permissions and access levels in your organization. Deletes a custom role. Preset roles cannot be deleted, and a role still assigned to users or groups must be unassigned first. A service account of a parent tenant can delete a descendant tenant's role by setting `X-Tenant-Id` to that tenant's customer ID. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_role4 of 5 parameters describedManage user permissions and access levels in your organization. Updates the `name`, `description` and/or `permissions` of a custom role. Only the fields present in the body change; `permissions` replaces the full list when present. Preset roles cannot be modified. A service account of a parent tenant can update a descendant tenant's role by setting `X-Tenant-Id` to that tenant's customer ID.
list_service_accounts2 of 2 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Returns every service account owned by the authenticated customer in a single unpaginated `items` array, in no guaranteed order. Requires the `serviceAccountViewer` permission.
create_service_account4 of 6 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Creates a service account owned by the authenticated customer. It cannot authenticate anything until it has an API token; mint one with the `api-tokens` sub-resource. Returns `409` when another service account of the customer already uses `name`. With `dryRun=true` the request goes through the same checks as a real create (name bounds and uniqueness, permission names, caller scope) and returns the same errors without creating anything. When the caller authenticates with a service account token, `createdBy`, `createdByEmail` and `createdByUserId` are `null`. Requires the `serviceAccountCreator` permission.
get_service_account1 of 2 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Returns a service account owned by the authenticated customer; an ID that belongs to another customer returns `404`. The `ETag` response header carries the value to send in `If-Match` on update and delete. Requires the `serviceAccountViewer` permission.
delete_service_account1 of 5 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Permanently deletes a service account and all of its API tokens, which stop authenticating immediately. Deleting an ID that no longer exists returns `404`. Requires the `serviceAccountManager` permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_service_account2 of 8 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Partially updates a service account with an `application/merge-patch+json` body (RFC 7396). Omitted or `null` fields stay unchanged; an explicit empty string clears `description`. `permissions` replaces the whole list, and `[]` removes every permission. With `dryRun=true` the request goes through the same checks as a real update (`If-Match`, name bounds and uniqueness, permission names, caller scope) and returns the service account as it would look after the patch, without changing anything. Requires the `serviceAccountManager` permission.
list_service_account_tokens2 of 3 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Returns the service account's non-deleted API tokens in a single unpaginated `items` array, at most 10. Secret material is never returned here — `accessToken` is shown only once, by the create operation. Requires the `serviceAccountViewer` permission.
create_service_account_token3 of 6 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Mints an API token for the service account and returns its `accessToken` once. The token inherits the service account's permissions as they stand at creation; there is no per-token scoping. Returns `409` when the service account already has a token of the same name, and `422` at the cap of 10 tokens. `dryRun=true` checks the name bounds only, then returns a preview without creating anything. It does **not** verify that the service account exists, that the name is unused, or that the account is under the token cap, so a dry run can succeed where the real create then returns `404`, `409` or `422`. Requires the `serviceAccountCreator` permission.
get_service_account_token1 of 3 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Returns one API token of the service account; an ID that belongs to another customer returns `404`. `accessToken` is not included — it is shown only once, by the create operation. Requires the `serviceAccountViewer` permission.
delete_service_account_token1 of 5 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Permanently deletes an API token, which stops authenticating immediately. This cannot be undone. Deleting an ID that no longer exists returns `404`. Requires the `serviceAccountManager` permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_service_account_token2 of 6 parameters describedManage non-human identities whose API tokens call the DoiT API with a fixed set of permissions. Moves the token between `active` and `disabled` by setting `state`. Disabling takes effect immediately: the token stops authenticating until it is re-enabled. Setting the state a token already has succeeds and changes nothing. The two directions are not symmetric. Disabling a token whose expiry has passed succeeds, but re-enabling an expired token returns `422` — expiry is final, and a new token has to be created instead. `deleted` and `expired` are not accepted values: a token is deleted through the delete operation, and expires on its own. With `dryRun=true` nothing is written and the response body is the token as it would look after the change, so a `422` here means a real request would also be refused. Requires the `serviceAccountManager` permission.
id_of_asset1 of 3 parameters describedManage cloud resources or services in your cloud environment. Updates an existing asset, such as G Suite/Workspace or Office 365 subscription, to add or remove licenses.
update_ticket3 of 4 parameters describedCreate and manage support tickets with DoiT. Partially updates a support request. Supports setting the request `status` and/or `assignee`. DoiT employees may set any of `open`, `pending`, `hold`, or `solved` and may set the `assignee`; customers may set only `solved` (parity with the console "mark as resolved" action) and may not set an assignee. `closed` is not settable via the API (Zendesk auto-closes from `solved`). The `assignee` is a DoiT-employee email, resolved server-side to a Zendesk agent; an email that does not resolve to an active agent returns `400`. At least one mutable field must be present. The response echoes the fields that were applied.
list_ticket_tags2 of 3 parameters describedCreate and manage support tickets with DoiT. Returns the tags currently set on a support request. DoiT employee (doer) callers receive the full tag set verbatim, including internal namespaces (e.g. `tier/*`, `synapse_*`). Customer callers receive only tags under the `customer_tag/` namespace, with that prefix stripped (e.g. a tag added as `billing` reads back as `billing`). Always present; empty array when the caller has no visible tags.
add_ticket_tags2 of 3 parameters describedCreate and manage support tickets with DoiT. Adds one or more tags to an existing support request. The operation is surgical — only the tags listed in the request are added; existing tags on the ticket are preserved. Re-adding a tag that is already present is a successful no-op. All submitted tags are normalized (trim + lowercase) before storage. For customers, the system additionally applies a `customer_tag/` namespace prefix to prevent collisions with internal DoiT process tags. The response echoes the actual stored strings so callers can verify the transform.
remove_ticket_tags2 of 3 parameters describedCreate and manage support tickets with DoiT. Removes one or more tags from an existing support request. The operation is surgical — only the tags listed in the request are removed; tags not listed are preserved. Removing a tag that is not present is a successful no-op. For customers, the system applies the same `customer_tag/` namespace mapping as on add, so a customer who added `my_tag` (stored as `customer_tag/my_tag`) can remove it by sending `my_tag`. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
get_statussheet_components8 of 10 parameters describedCloud Diagrams visualize your cloud infrastructure and resource relationships. Returns the specified components of a diagram layer. Provide at least one component type with one or more IDs in the request body (for example, `node` or `element`).
export_cloud_diagram_json1 of 2 parameters describedCloud Diagrams visualize your cloud infrastructure and resource relationships. Exports the full content of a diagram layer as a structured JSON document, including all components and export metadata.
list_cloud_diagram_layer_snapshots2 of 6 parameters describedCloud Diagrams visualize your cloud infrastructure and resource relationships. Returns the list of saved snapshots for the specified diagram layer.
get_cloud_diagram_layer_snapshot1 of 3 parameters describedCloud Diagrams visualize your cloud infrastructure and resource relationships. Returns a single snapshot of the specified diagram layer identified by its ID.
ava_feedback3 of 4 parameters describedInteract with Ava, DoiT's AI-powered cloud assistant. Submit feedback on an Ava answer to help improve response quality.
delete_ava_conversation1 of 2 parameters describedInteract with Ava, DoiT's AI-powered cloud assistant. Deletes an Ava conversation by its ID. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
post_insight_results2 of 2 parameters describedManage cloud insights representing recommendations and findings for cloud resources. Creates or updates multiple insights in a single batch request. Each insight in the batch includes its metadata and resource results inline. For granular control over insight metadata and resource results independently, use the single-insight and resource-results endpoints instead.
delete_insight_results1 of 2 parameters describedManage cloud insights representing recommendations and findings for cloud resources. Deletes all insights matching the specified key from the batch source. This removes the insight and all its associated resource results. For single-insight deletion, use `DELETE /source/{sourceID}/insight/{insightKey}` instead. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_insight_result1 of 3 parameters describedManage cloud insights representing recommendations and findings for cloud resources. Permanently deletes a single insight and all its associated resource results. Only insights created via the public API can be deleted. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
post_insight_resource_results2 of 5 parameters describedManage cloud insights representing recommendations and findings for cloud resources. Replaces all resource results for the specified insight. Any existing unresolved resource results not present in the new set will be removed. The response includes server-computed fields (severity, resolved, enhancement) for each resource result. To delete all resource results, send an empty array.
list_composer_recipes1 of 6 parameters describedBeta. Read-only access to Composer recipes and their results. A recipe evaluates your cloud resources against a set of conditions; each result is a finding on one affected resource, and published recipes surface as proprietary Insights in the Console. Returns the Composer recipes that have results in your recently scanned cloud accounts, with counts of those results by status and their estimated savings. Recipes with no such results are not listed. Dismissed recipes are listed with `status: dismissed` and every count set to 0. Recipes are sorted by `severity`, descending, by default. Ties break by title (case-insensitive), then by `id`. `filter` is one string of `key:value` clauses: `,` separates alternative values for one key (OR) and `|` separates keys (AND), for example `severity:critical,high|provider:aws,gcp`. Because `,` and `|` are separators, a value itself can't contain them. Supported keys: - `provider`: one or more of `aws`, `azure`, `azure_ad`, `gcp`, `general`, `google_cloud_source`, `google_workspace`, `k8s`, `oci`, `vmware`. - `severity`: one or more of `critical`, `high`, `medium`, `low`. - `pillar`: one or more of `cost`, `operations`, `performance`, `security`, `compliance`. `compliance` matches recipes tagged with at least one compliance standard. - `has_active_results`: exactly one of `true` or `false`. - `allocation`: up to 10 distinct allocation IDs from `GET /analytics/v1/allocations`. Lists only recipes with results on resources in any of those allocations; counts, savings and `rowCount` then cover only those resources. An allocation you can't view returns `404`; if access can't be checked, the request returns `503` rather than unfiltered data. Requests are always served for the customer your API token belongs to. To list the results of one recipe, use its `id` with `GET /insights/v2/recipes/{recipeId}/results`. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page. Each recipe includes its remediation text, so this tool requests 20 recipes per page unless maxResults is set (the API's own default is 50; pages of 50 or more can exceed the MCP result size limit).
list_composer_recipe_results1 of 7 parameters describedBeta. Read-only access to Composer recipes and their results. A recipe evaluates your cloud resources against a set of conditions; each result is a finding on one affected resource, and published recipes surface as proprietary Insights in the Console. Returns the results of one Composer recipe: one finding per affected resource, with the resource's account, region, tags and cost metrics. An unknown recipe, one your customer isn't entitled to, and a dismissed recipe all return `200` with an empty `items` list and `rowCount: 0`. By default (`last_scan_only:true`) only results reported by the most recent scan of each recently scanned account are returned. A resolved result keeps the ID of the last scan that reported it, so resolved results rarely appear by default; add `last_scan_only:false` to include them and results from earlier scans. `rowCount` can therefore be lower than the recipe's `totalResultsCount`. Results are sorted by `detection_time`, descending, by default. Ties break by `id`. `filter` is one string of `key:value` clauses: `,` separates alternative values for one key (OR) and `|` separates keys (AND), for example `region:us-east-1,us-west-2|status:active`. Because `,` and `|` are separators, a value itself can't contain them. Supported keys: - `account_id`: one or more cloud account IDs, matched exactly. - `region`: one or more cloud regions, matched exactly. - `issued_resource_name`: one or more names of the affected resource, matched exactly. - `related_resource_name`: one or more names of related resources (for example an attached IAM policy), each matched as a substring anywhere in the result's related-resource details. - `status`: exactly one of `active` (not resolved and not snoozed), `snoozed`, `resolved` or `all`. Omitting it is the same as `all`. Combine `resolved` with `last_scan_only:false`; with the default it usually returns nothing. - `last_scan_only`: exactly one of `true` or `false`. Defaults to `true`, which returns only results reported by each recently scanned account's most recent scan, and so rarely includes resolved results. `false` returns results from every scan and account, including resolved ones. - `allocation`: up to 10 distinct allocation IDs from `GET /analytics/v1/allocations`. Returns only results on resources in any of those allocations. An allocation you can't view returns `404`; if access can't be checked, the request returns `503` rather than unfiltered data. Requests are always served for the customer your API token belongs to. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
create_account_role6 of 6 parameters describedManage cloud provider connections and check feature availability for connected accounts. Creates or updates a CloudConnect document for an AWS account. Unlike the CloudFormation variant, this endpoint does not update Firestore channel documents or require a CloudFormation stack ID.
update_aws_feature4 of 5 parameters describedManage cloud provider connections and check feature availability for connected accounts. Updates an AWS feature for an existing CloudConnect account. Unlike the CloudFormation variant, this endpoint does not update Firestore channel documents, require a CloudFormation stack ID, or handle StackSet member role ARNs.
delete_account_role1 of 2 parameters describedManage cloud provider connections and check feature availability for connected accounts. Deletes a CloudConnect document for an AWS account. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
delete_cloudflow_connection1 of 3 parameters describedManage cloud provider connections used in CloudFlow workflows (AWS and GCP). Deletes a connection. Returns 409 if the connection is referenced by one or more flows. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
trigger_cloudflow_flow1 of 2 parameters describedManage CloudFlow. Starts a run of a **published** flow whose first node is a webhook, scheduled, or manual trigger. A draft flow is rejected with `422` — use `actions/test-run` to run one. No `Idempotency-Key` is required. This is a state transition, not a resource creation. The response is a snapshot taken at dispatch, so `status` is always `pending` and the timing fields are not yet populated. Read the run back through `GET /cloudflow/v1/flows/{flowId}/runs/{runId}` to follow its progress. A flow holds a concurrency lock while it runs, so triggering one that is already running returns `409` with the active run embedded in the problem body — no second lookup needed. The current generated MCP schema exposes no arbitrary trigger payload field; the API uses an empty payload when omitted. trigger_cloud_flow accepts a webhook payload for published webhook flows.
stop_cloudflow_flow1 of 2 parameters describedManage CloudFlow. Stops the run currently in progress for the given flow. The run is identified from the flow alone — no run ID is needed, since a flow can only have one run active at a time. No `Idempotency-Key` is required. This is a state transition, not a resource creation. Returns `409` when the flow has no run in progress, which includes a run that reached a terminal state between this request and the stop attempt.
test_run_cloudflow_flow1 of 4 parameters describedManage CloudFlow. Runs a flow once as a test, and **accepts an unpublished (draft) flow** — unlike `actions/trigger`, which requires the flow to be published. Use this to verify a newly authored or edited flow before publishing it. Execution is identical to a production run: the same graph, the same bound connections, the same credentials, and the same approval behaviour. An approval-gated node still parks the run and its side effect still waits for a real approval — there is no request that skips one. The run is recorded as a test, so it does not appear in run history, does not count towards dashboard statistics, does not become a dashboard widget's data source, and does not consume a scheduled-run budget. It does hold the flow's concurrency lock, so a `409` is returned while the flow is already running. The flow's first node must be a webhook, scheduled, or manual trigger. Before dispatching, the flow is validated with the same checks publish applies — a draft has never been through them. A flow that fails returns `422` listing every offending node at once, so all of them can be fixed in one pass. Poll the `Location` URL to follow the run and read what each node produced. Pass `?dryRun=true` to validate the flow without starting a run. Generated codeNode code may fail silently or error at run time despite passing validation. With dryRun this call shows only that the flow is well-formed; without dryRun it executes real actions even on drafts. A completed run's per-node output (get_cloudflow_flow_run) shows whether it works. The current generated MCP schema exposes no arbitrary trigger payload field; the API uses an empty payload when omitted. Idempotency-Key is required even with dryRun. Same key/request replays within 24 hours; different request fails with 422, an in-progress match with 409. Dry-runs validate existing fingerprints without storing a replay. The API fingerprints MCP tracking parameters; a changed client/server version can cause a same-key conflict. Keep the original request context and key. If an HTTP failure has only generic text, do not infer a status or retry automatically. Full CloudFlow authoring guide: MCP resource doit://docs/cloudflow-authoring.
list_cloudflow_flow_runs1 of 5 parameters describedManage CloudFlow. Returns a flow's runs, newest first. Use `mode` to separate test runs from production ones — test runs are included by default. Per-node detail is not included here; fetch a single run to read what each node consumed and produced. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
get_cloudflow_flow_run1 of 3 parameters describedManage CloudFlow. Returns a run's status and, for each node, the JSON it consumed and produced. This is how you find out *why* a run failed, or that it "succeeded" while producing the wrong data. **`input` is null for most node types, and that is not an error.** Only action nodes — the AWS, GCP, Azure, Oracle, DoiT and admin operations — record their inputs. Transform, code, branch, switch, datastore, subflow and trigger nodes record none, so their `input` is always null. `output` is recorded by every node that finishes, so read a transform's behaviour from its `output`. Payloads appear as soon as a node reports a terminal status, so a poll loop can read results while later nodes are still running. Any value the node's schema marks sensitive is replaced with a redaction marker; credentials and connection configuration never appear. Each `input` and `output` is capped at 64KB. When a payload exceeds that, whole entries are dropped from the end, `truncated` is true, and `totalBytes` reports the untruncated size — nothing is silently cut, and what you receive is always valid JSON. Runs belonging to another tenant, or to a different flow, return `404`. Nodes inside a fan-out currently report only the last path to finish.
export_cloudflow_flow1 of 3 parameters describedManage CloudFlow. Serializes the flow — plus every flow it references through subflow nodes — into a tenant-neutral, credential-free JSON bundle that can be imported into any tenant with the import operation. Tenant-scoped references (connections, Datastore tables, global variables) are declared as named requirements and rebound at import time; policy and Slack-channel references cannot travel and are recorded as unsupported references. The bundle never contains credentials, tenant identifiers, schedules, or execution state. codeNode: JavaScript (default) uses $nodes["<node name>"] and $variables; Python uses nodes and variables. Upstream values are lists. A top-level return produces {message: value}; no return gives JS {} / Python {message: null}. Bare input is not injected; accessing it as upstream data fails the node. A schema (JSON Schema string) is required. Full CloudFlow authoring guide: MCP resource doit://docs/cloudflow-authoring.
import_cloudflow_flow3 of 6 parameters describedManage CloudFlow. Creates every flow of a previously exported bundle in the authenticated tenant. Imports are create-only: each call creates new draft flows with new IDs — nothing is published and no schedule is activated until the target tenant publishes. Requirements declared by the bundle are resolved through `bindings` (requirement key → target-tenant resource ID). Unbound connections and Datastore tables leave the referencing nodes flagged incomplete; unbound global variables are auto-created. Pass `options.createMissingTables: true` to create missing Datastore tables from the schemas embedded in the bundle (structure only, never row data). **Dry-run**: pass `?dryRun=true` to validate without writing. The response is an import plan: per-requirement resolutions with candidate bindings in the target tenant, the flows that would be created, and every validation issue at once. Idempotency-Key is required even with dryRun. Same key/request replays within 24 hours; different request fails with 422, an in-progress match with 409. Dry-runs validate existing fingerprints without storing a replay. codeNode: JavaScript (default) uses $nodes["<node name>"] and $variables; Python uses nodes and variables. Upstream values are lists. A top-level return produces {message: value}; no return gives JS {} / Python {message: null}. Bare input is not injected; accessing it as upstream data fails the node. A schema (JSON Schema string) is required. The API fingerprints MCP tracking parameters; a changed client/server version can cause a same-key conflict. Keep the original request context and key. If an HTTP failure has only generic text, do not infer a status or retry automatically. Full CloudFlow authoring guide: MCP resource doit://docs/cloudflow-authoring.
list_aws_organizations1 of 4 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns all AWS organizations (accounts) accessible to the authenticated tenant. Use as the entry point to discover AWS organization account IDs, and organization-level onboarding status of the available commitment types and savings metrics. Each item includes metadata, trailing 30-day aggregate statistics, precomputed YTD/lifetime savings totals per Savings Plan (SP) type, and estimated monthly potential savings (`monthlyPotentialSavings`) per SP type from the latest projection. Sum across items for customer-level totals. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
get_aws_organization1 of 3 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a single AWS organization with the same list-item fields as List AWS Organizations, plus the Overview time series. Use this when you need a single organization's Console Overview in one call (identity and onboarding status, 30-day ESR and savings, YTD/lifetime totals, monthly potential savings, and the data behind Cost Summary and Commitment Coverage charts) without fetching every organization. Fields that drive the Overview tab in the DoiT console: - `stats30d`: last 30 days ESR and realized savings per SP type (ESR and Savings cards). - `monthlyStats`: last 6 calendar months of ESR, on-demand cost, and cost with savings per SP type (Cost Summary chart, and month-over-month card trends). - `dailyCoverage`: last 30 days of commitment coverage breakdown per SP type (Commitment Coverage chart). - `savingsTotals`: year-to-date and lifetime realized savings per SP type (shown under the Savings card). Lifetime is bounded by PerfectScale for Commitments onboarding start. - `monthlyPotentialSavings`: estimated monthly additional savings per SP type from the latest purchase projection.
list_aws_member_accounts1 of 5 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns all member AWS accounts under the specified AWS organization that have active or historical commitment coverage. Includes 30-day statistics and estimated monthly potential savings (`monthlyPotentialSavings`) per Savings Plan (SP) type. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
get_aws_member_account1 of 4 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a single member AWS account with the same list-item fields as List member accounts, plus the Overview time series. Use this when you need a single members Console Overview in one call (identity and onboarding status, 30-day ESR and savings, YTD/lifetime totals, monthly potential savings, and the data behind Cost Summary and Commitment Coverage charts) without fetching every member account. Fields that drive the Overview tab in the DoiT console: - `stats30d`: last 30 days ESR and realized savings per SP type (ESR and Savings cards). - `monthlyStats`: last 6 calendar months of ESR, on-demand cost, and cost with savings per SP type (Cost Summary chart, and month-over-month card trends). - `dailyCoverage`: last 30 days of commitment coverage breakdown per SP type (Commitment Coverage chart). - `savingsTotals`: year-to-date and lifetime realized savings per SP type (shown under the Savings card). Lifetime is bounded by the parent organization's PerfectScale for Commitments onboarding start. - `monthlyPotentialSavings`: estimated monthly additional savings per SP type from the latest purchase projection.
list_aws_savings_plans1 of 7 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a paginated list of Savings Plans for the specified AWS organization. Optionally filter by plan type (`type`) and state (`status`). Omit both filters to return all plans for the AWS organization. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_aws_reserved_instances1 of 10 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a paginated list of Reserved Instances (RIs) for the specified AWS organization. Optionally filter by state, instance type, instance family, region, and offering class. Omit filters to return all RIs for the AWS organization. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_aws_recommendations1 of 3 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns commitment purchase recommendations for the AWS organization, keyed by commitment type (`compute`, `database`). A commitment type is present only when it is onboarded and a recommendation is available.
get_aws_recommendation1 of 5 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns the recommendation for one commitment type (`serviceId`) on the AWS organization, including analysis metrics and time-bucketed eligible spend. Use `granularity` to choose the eligible-spend bucket size (defaults to `day`).
list_aws_planned_purchases1 of 6 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns planned purchases (laddering projections) for the AWS organization. One item per commitment type that has a projection available (typically `compute` and/or `database`; up to four commitment types as PerfectScale for Commitments expands). With no filters, returns all available planned-purchase items for the AWS organization in stable commitment-type order (`compute`, then `database`, then any future commitment types in enum order). When a filtered commitment type has no planned purchases, the response is an empty `items` array (not `404`). Partial items return only the fields available at response time. `404` is returned only when the AWS organization does not exist or the caller cannot access it. An AWS organization that is not onboarded for PerfectScale for Commitments still returns `200` with an empty `items` array when no planned purchases exist — use `GET /ps4commitments/v1/aws/organizations` (or get-by-id) for `onboardingStatus`. **Pagination**: results are returned in stable commitment-type order (`compute`, then `database`, then any future commitment types in enum order). Use `maxResults` to limit page size (default 50, max 500). When more items remain, the response includes a non-null `pageToken`; pass it unchanged on the next request with the same query parameters (`service`, `maxResults`). `rowCount` is the number of items in this page. An invalid `pageToken` returns `400` with code `pagination_token_invalid`; an expired token returns `400` with code `pagination_token_expired`. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_aws_organizations_settings1 of 4 parameters describedEvaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns one item per onboarded AWS organization. Each item includes that AWS organization's commitments purchasing account (`purchaseAccountId`) and commitment settings for each commitment type activated on that AWS organization (`compute`, `database`). Commitment settings cover recommendation and automation preferences (policy, term, payment option, automation mode, commitment limits, and related fields). They are stored independently for each AWS organization and commitment type. Each item includes that organization's `purchaseAccountId` and activated commitment types. In the DoiT Console, commitment settings are edited on an account's Settings tab and apply only to that AWS organization and commitment type; the purchasing account is set per AWS organization on Accounts Settings. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_billing_transfer_program_management_accounts1 of 4 parameters describedManage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts. Lists the caller's program management accounts (PMAs) and the reseller tenants mapped to each one, including AWS Organizations handshake status per account. Distributor-only. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
get_billing_transfer_program_management_accounts_status1 of 2 parameters describedManage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts. Lightweight polling surface for the onboarding wizard: returns each of the caller's PMAs with only its IAM status/diff and timestamps — no tenant fan-out, no handshake aggregation, no pagination. Distributor-only.
list_billing_transfer_end_customers2 of 6 parameters describedManage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts. Lists the end-customer AWS account mappings under a reseller's program management account, identified by `dpmaId` and `resellerPmaAccountId`. Callable by the reseller who owns the PMA or the distributor who owns the DPMA.
list_billing_transfer_end_customers_by_reseller2 of 5 parameters describedManage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts. Same result as `GET /billingtransfer/v1/end-customers`, identified by `resellerPmaAccountId` alone (no `dpmaId` needed). Callable by the reseller who owns the PMA or the distributor who owns its DPMA.
list_billing_transfer_reseller_accounts2 of 3 parameters describedManage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts. Lists every reseller program management account (RPMA) node belonging to the calling reseller, with handshake state and status but without end-customer tenants — the reseller-tier analog of `GET /billingtransfer/v1/programmanagementaccounts`.
list_billing_transfer_reseller_accounts_with_tenants2 of 4 parameters describedManage AWS billing-transfer mappings between distributors and resellers and between resellers and end customers, and list program management accounts. Lists every reseller PMA node belonging to the calling reseller, each with the end-customer tenants connected under it — the reseller-tier analog of `GET /billingtransfer/v1/programmanagementaccounts`. `region`, `iamStatus` and `lastRefreshTime` are inherited from the parent DPMA root; the reseller node itself carries no IAM/region metadata of its own.
list_geographic_access_countries2 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Returns the canonical ISO 3166-1 alpha-2 country catalogue used by geographic access policies.
list_geographic_access_custom_regions2 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Returns the ready custom regions owned by the authenticated tenant. Requires the UsersManager permission.
create_geographic_access_custom_region1 of 4 parameters describedManage country-based access to tenants in your customer hierarchy. Creates a custom region owned by the authenticated tenant. The tenant must be a customer-hierarchy root. Requires the UsersManager permission.
get_geographic_access_custom_region1 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Returns a custom region owned by the authenticated tenant. Requires the UsersManager permission.
delete_geographic_access_custom_region1 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Deletes a custom region owned by the authenticated tenant. Assigned regions cannot be deleted. Requires the UsersManager permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_geographic_access_custom_region1 of 5 parameters describedManage country-based access to tenants in your customer hierarchy. Updates the name, country membership, or both for a custom region owned by the authenticated tenant. Requires the UsersManager permission.
list_customer_groups2 of 3 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Returns the ready customer groups owned by the authenticated tenant. Requires the UsersManager permission.
create_customer_group1 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Creates a customer group owned by the authenticated tenant. Requires the UsersManager permission.
get_customer_group1 of 3 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Returns a customer group owned by the authenticated tenant. Requires the UsersManager permission.
delete_customer_group1 of 3 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Deletes a customer group owned by the authenticated tenant. Groups with assigned users or user groups cannot be deleted. Requires the UsersManager permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
update_customer_group1 of 5 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Updates the name, customer membership, or both for a customer group owned by the authenticated tenant. Requires the UsersManager permission.
list_customer_group_users2 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Returns the users assigned to a customer group owned by the authenticated tenant, sorted by user ID. Requires the UsersManager permission.
assign_customer_group_user1 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Assigns a user to a customer group owned by the authenticated tenant. Requires the UsersManager permission.
unassign_customer_group_user1 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Unassigns a user from a customer group owned by the authenticated tenant. Requires the UsersManager permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
list_customer_group_user_groups2 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Returns the user groups assigned to a customer group owned by the authenticated tenant, sorted by user-group ID. Requires the UsersManager permission.
assign_customer_group_user_group1 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Assigns a user group owned by the authenticated tenant to a customer group owned by that tenant. Membership changes in the user group apply without reassigning it. Requires the UsersManager permission.
unassign_customer_group_user_group1 of 4 parameters describedManage explicit, named groups of downstream customers and the users scoped to them. Unassigns a user group from a customer group owned by the authenticated tenant. Requires the UsersManager permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
get_customer_geographic_access_scope1 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Returns the geographic scope for a target customer. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Targets outside that hierarchy are returned as not found. Requires the UsersManager permission.
update_customer_geographic_access_scope1 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Atomically replaces the geographic scope for a target customer. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Repeating an identical request is idempotent. Requires the UsersManager permission.
delete_customer_geographic_access_scope1 of 3 parameters describedManage country-based access to tenants in your customer hierarchy. Clears the geographic scope for a target customer, leaving it unassigned. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Repeating the request is idempotent. Requires the UsersManager permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
get_user_geographic_access_scope1 of 4 parameters describedManage country-based access to tenants in your customer hierarchy. Returns the geographic scope assigned to a user who belongs to the target customer. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Targets outside that hierarchy are returned as not found. Requires the UsersManager permission.
update_user_geographic_access_scope1 of 4 parameters describedManage country-based access to tenants in your customer hierarchy. Atomically replaces the geographic scope assigned to a user who belongs to the target customer. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Repeating an identical request is idempotent. Requires the UsersManager permission.
delete_user_geographic_access_scope1 of 4 parameters describedManage country-based access to tenants in your customer hierarchy. Clears the geographic scope assigned to a user who belongs to the target customer, leaving it unassigned. The authenticated tenant must be the hierarchy root, and the target must be that root customer or one of its child customers. Repeating the request is idempotent. Requires the UsersManager permission. Two-step: a call with valid arguments deletes nothing. It returns `status: "approval_required"` with a summary of the exact request and a one-time `approvalToken`. The saved request runs only when `confirm_action` is called with that token after the user approves the summary. The token is bound to the caller and expires after 5 minutes.
list_gcp_billing_accounts1 of 4 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns all GCP Billing Accounts accessible to the authenticated tenant. Use as the entry point to discover GCP billing account IDs, and billing-account-level onboarding status of the available product lines and savings metrics. Each item includes metadata, CUD export health, trailing 30-day aggregate statistics, and precomputed YTD/lifetime savings totals per product line. Sum across items for customer-level totals. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
get_gcp_billing_account1 of 3 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a single GCP Billing Account with the same list-item fields as List GCP Billing Accounts, plus the Overview time series. Use this when you need a single billing account's Console Overview in one call (identity and onboarding status, 30-day ESR and savings, YTD/lifetime totals, CUD export health, and the data behind Cost Summary and CUD Coverage charts) without fetching every billing account. Fields that drive the Overview tab in the DoiT console — each is an array with one entry per product line (`service` of `compute` or `cloud_sql`): - `stats30d`: last 30 days ESR and realized savings per product line (ESR and Savings cards). - `monthlyStats`: last 6 calendar months of ESR, on-demand cost, and cost with savings per product line (Cost Summary chart, and month-over-month card trends). - `dailyCoverage`: last 30 days of CUD coverage breakdown per product line (CUD Coverage chart). - `savingsTotals`: year-to-date and lifetime realized savings per product line (shown under the Savings card). Lifetime is bounded by PerfectScale for Commitments onboarding start.
list_gcp_spend_cuds2 of 8 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a paginated list of spend-based CUDs for the billing account. Optionally filter by CUD state (`status`); omit to return CUDs in all states. **`gcp_service` and `region` filters**: `gcp_service` narrows results to one product line's coverage sub-type (`compute` or `cloud_sql`); `region` additionally narrows to one region scope and requires `gcp_service` — a request with `region` but no `gcp_service` returns `400` with code `gcp_service_required`. A `region` that is malformed or incompatible with `gcp_service` (`compute` is `global`-only, `cloud_sql` is regional-only) returns `400` with code `validation_failed`; a well-formed, compatible region with no matching CUDs returns `200` with an empty `items` array. Note the `region` query parameter uses the `lower_snake_case` wire form (`us_central1`), while each item's `region` field echoes the raw provider value (`us-central1`). This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_gcp_resource_cuds1 of 6 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns a paginated list of resource-based (vCPU / memory) CUDs for the billing account. Optionally filter by CUD state (`status`). Omit to return CUDs in all states. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_gcp_recommendations3 of 6 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns commitment purchase recommendations for the billing account, filtered to the term preferred in each product line's settings (`preferredCommitmentPeriod`). **`gcp_service` and `region` filters**: omit both to return recommendations for all product lines (`compute`, `cloud_sql`) across all their regions. Supply `gcp_service` alone to return all regions for that service; supply both to return a single service/region scope. `region` requires `gcp_service` — a request with `region` but no `gcp_service` returns `400` with code `gcp_service_required`. A `region` that is malformed or incompatible with `gcp_service` (`compute` is `global`-only, `cloud_sql` is regional-only) returns `400` with code `validation_failed`; a well-formed, compatible region with no data returns `200` with an empty `items` array. `404` is returned only when the billing account does not exist or the caller cannot access it. A billing account with no matching recommendation documents returns `200` with an empty `items` array.
get_gcp_recommendation2 of 6 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns the recommendation for one product line (`gcp_service`) and region scope on the GCP billing account, including analysis metrics and time-bucketed eligible spend. Use `granularity` to choose the eligible-spend bucket size (defaults to `day`). **`region`**: optional for `compute`, defaulting to `global` (its only scope). Required for `cloud_sql` — omitting it returns `400` with code `validation_failed`, as does a malformed region or one incompatible with `gcp_service` (`cloud_sql` never uses `global`). A well-formed region the billing account has never had eligible spend in returns `404` with code `not_found` — the scope does not exist, same as an unknown billing account. When the scope exists but no stored recommendation matches, the response is `200` with `recommendation` omitted and `estimatedEquivalentRecommendedCommitment` of `0`.
list_gcp_planned_purchases2 of 7 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns the laddering projections for the billing account, grouped by PS4C product line (`service`) and region. Each service group lists one entry per available `gcp-purchases-projection` document for that scope (`compute` scopes are `global`; `cloud_sql` scopes are per-region). With no filters, returns all existing projection documents in stable order: service groups ordered `compute` first, then `cloud_sql`; within each group, regions sorted with `global` first, then remaining regions alphabetically. Services with no projection documents are omitted (not returned as empty groups). When a filter matches no documents, the response is an empty `items` array (not `404`). Partial projection documents return only the fields available in storage. **`gcp_service` and `region` filters**: omit both to return all available services and their regions; supply `gcp_service` alone to return all regions for that service; supply both to return a single service/region scope. `region` requires `gcp_service` — a request with `region` but no `gcp_service` returns `400` with code `gcp_service_required`. Invalid `gcp_service` or `region` values return `400` with code `validation_failed`. `404` is returned only when the billing account does not exist or the caller cannot access it. A billing account that is not onboarded for PS4C still returns `200` with an empty `items` array when no projection documents exist — use `GET /ps4commitments/v1/gcp/billing-accounts` (or get-by-id) for onboarding status. **Pagination**: results are paginated by **service group** (a whole group is never split across pages). Groups keep the stable service order above. Use `maxResults` to limit page size (default 50, max 500). When more groups remain, the response includes a non-null `pageToken`; pass it unchanged on the next request with the same query parameters (`gcp_service`, `region`, `maxResults`). `rowCount` is the number of service groups in this page. An invalid `pageToken` returns `400` with code `pagination_token_invalid`; an expired token returns `400` with code `pagination_token_expired`. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_gcp_billing_accounts_settings1 of 4 parameters describedEvaluate current GCP commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments. Returns one item per onboarded GCP Billing Account. Each item includes that billing account's recommendation and automation engine settings for each product line activated on it, per region scope: one `global` entry for `compute`, and one entry per known region for `cloud_sql`. Cloud SQL regions come from the billing account's persisted settings: a region is added when eligible spend is first seen there and is never removed, so its settings entry remains listed even if spend later drops to zero. Items are sorted by `billingAccountId`; within an item, `services` lists `compute` before `cloud_sql`, with `cloud_sql` regions sorted alphabetically. Settings are stored independently on each billing account. Existing customer-level settings are copied lazily when an account is first read or initialized; if no valid legacy value exists, the complete backend defaults are materialized once on the account. Only product lines that are activated/onboarded for a given billing account are returned. In the DoiT Console, these settings are edited on an account's Settings tab. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
list_commitment_policies1 of 4 parameters describedCloud-agnostic PerfectScale for Commitments resources — commitment policies shared by AWS and GCP. Returns every commitment policy available to the tenant: the three built-in policies (`conservative`, `balanced`, `max_savings`) followed by the tenant's own custom policies. Commitment policies are cloud-agnostic. A single catalog is shared by AWS and GCP, and the same policy may be assigned to AWS and GCP product lines alike. Built-in policies are listed first, ordered from least to most aggressive target coverage; custom policies follow in creation order. Percentage parameters are expressed as `1`–`100`, as entered in the DoiT Console. This differs from the coverage and utilization fields on recommendations and inventory, which are fractions from 0 to 1. This endpoint is read-only. Custom policies are created, edited and deleted in the DoiT Console on the Commitment Policies page. This endpoint is paginated: a response with a non-empty `pageToken` has more results, returned when that value is passed as the `pageToken` parameter. A missing, null, or empty `pageToken` marks the last page.
get_commitment_policy1 of 3 parameters describedCloud-agnostic PerfectScale for Commitments resources — commitment policies shared by AWS and GCP. Returns one commitment policy by id, with its creation and last-update times and the list of account × product-line scopes it is explicitly assigned to across AWS and GCP. `assignments` lists explicit assignments only. An account whose settings have not yet been materialized falls back to `balanced` implicitly and does not appear here, even though the settings endpoints report it as `balanced`. On AWS the assignment is currently recorded per tenant and applied to every onboarded organization, so each organization appears once per product line. The list is not paginated. Resolving assignments reads every onboarded account on both clouds. If either cloud cannot be queried the request fails rather than returning a partial list.
query_attribute_workloads_table2 of 11 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns one page of rows of Kubernetes workload cost, grouped by `dimension`, for a date range. Each row has its cost, its change against the previous period of the same length, and the related values for that dimension (for example the clusters and accounts of a namespace). Use this for granular rows ("top 10 workloads by cost", "which namespaces grew"). Use `queryAttributeWorkloadsStats` for totals and the total row count, and `queryAttributeWorkloadsOverTime` for a time series. Rows of the `workload` dimension carry a `workloadId`: pass it to the `/attribute/v1/workloads/w/*` operations to see that one workload's cloud resources. The request body holds the filters; this operation only reads data. Build filter values with `listAttributeWorkloadsFilterValues`. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
query_attribute_workloads_stats2 of 7 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns aggregated totals for a date range: the total cost, the number of workloads, the number of distinct `dimension` values (the row count of `queryAttributeWorkloadsTable` for the same request), and the percent change of the total cost against the previous period of the same length. Use this for "how much did workloads cost" or "how many namespaces", and to know how many pages the table has. Use `queryAttributeWorkloadsTable` for the rows. The request body holds the filters; this operation only reads data. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
query_attribute_workloads_over_time2 of 10 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns a cost time series grouped by `dimension`: the top `limit` values by cost, each as its own series, plus one "Others" series that sums the rest. Use this for trends and charts ("daily cost of the top 5 namespaces last month"). Use `queryAttributeWorkloadsTable` for rows with totals per value, and `queryAttributeWorkloadsStats` for one total. The request body holds the filters; this operation only reads data. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
get_attribute_workload_details2 of 3 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Decodes a `workloadId` into the workload's name, type, namespace, cluster and account. It reads no cost data and takes no date range. Use it to show which workload a `workloadId` names. Get a `workloadId` from a `workload` row of `queryAttributeWorkloadsTable`. An ID that does not decode returns 404. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
query_attribute_workload_resources_table3 of 10 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns one page of the cloud resources one workload used in a date range, one row per resource, with the workload's cost on it, the change against the previous period, and `accountability`: the workload's percent of the resource's total cost. Use this for "which resources drive the cost of workload X". It is the `resource` dimension of `queryAttributeWorkloadsTable`, limited to the workload in `workloadId`. Use `queryAttributeWorkloadResourcesStats` for totals and the row count, and `queryAttributeWorkloadResourcesOverTime` for a time series. Get `workloadId` from a `workload` row of `queryAttributeWorkloadsTable`. An ID that does not decode returns 404. The request body holds the filters; this operation only reads data. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
query_attribute_workload_resources_stats3 of 6 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns aggregated totals for one workload in a date range: its total cost, the number of cloud resources it used (`dimensionRowCount`, the row count of `queryAttributeWorkloadResourcesTable`), and the percent change of the total against the previous period of the same length. Use `queryAttributeWorkloadResourcesTable` for the resource rows. Get `workloadId` from a `workload` row of `queryAttributeWorkloadsTable`. An ID that does not decode returns 404. The request body holds the filters; this operation only reads data. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
query_attribute_workload_resources_over_time3 of 9 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns a cost time series of one workload, split by cloud resource: the top `limit` resources by cost, each as its own series, plus one "Others" series that sums the rest. Use this for the trend of one workload's cost. Use `queryAttributeWorkloadResourcesTable` for rows and `queryAttributeWorkloadResourcesStats` for totals. Get `workloadId` from a `workload` row of `queryAttributeWorkloadsTable`. An ID that does not decode returns 404. The request body holds the filters; this operation only reads data. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_workload_non_network_resource_types2 of 5 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the names of the resource types (billed services) that one workload used in a date range and that are not network cost, highest cost first, at most 50. It returns no cost amounts, for any customer. Use it to tell a freemium customer, who sees network cost only, which other cost types the workload has. For costs, use `queryAttributeWorkloadResourcesTable`. Get `workloadId` from a `workload` row of `queryAttributeWorkloadsTable`. An ID that does not decode returns 404. This operation only reads data. Freemium customers (no paid Attribute plan) can only ask for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_workloads_cloud_providers3 of 7 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the distinct cloud providers that billed the resources matched by the filters in a date range (`resourceCloudProvider`, the cloud of the billed resource, not of the cluster). Send `workloadId` to limit it to one workload. Use it to know which clouds a selection spans, for example before asking for `hour` granularity: Azure data is daily only. For the cloud of the clusters, use `listAttributeWorkloadsFilterValues` with `platformCloudProvider`. The request body holds the filters; this operation only reads data. A `workloadId` that does not decode returns 404. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
get_attribute_workloads_signals1 of 2 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns three lists of workloads that need attention, grouped by workload name and type. Each list has every workload that meets its rules, ranked: - `spike`: cost grew a lot against the week before. - `new`: workloads first seen in the last two weeks with real cost. - `network`: network cost grew a lot against the week before (the same rules as `spike`, applied to network cost). The windows are fixed UTC days and do not depend on any date range: the current window is today minus 8 days to today minus 2 days, and the previous window is the 7 days before it. `window` and `thresholds` in the response give the exact dates and rules. Use this for "what changed" or "what should I look at". To get the matching rows or totals over your own date range, pass `signal=spike|new|network` to `queryAttributeWorkloadsTable`, `queryAttributeWorkloadsStats` or `queryAttributeWorkloadsOverTime`. Freemium customers (no paid Attribute plan) see network cost only, so all three lists use network cost for them. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
get_attribute_workloads_cost_data_status1 of 2 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns `hasWorkloadData`: whether the customer has any Kubernetes workload cost data yet. Call it first when other operations return empty results, to tell "no data in this date range or filter" from "no workload data at all" (for example, the Attribute sensor is not installed yet or its first data has not arrived). Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_workloads_filter_values2 of 8 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the distinct values of one filter field in a date range, sorted case-insensitively, one page at a time. Use it to find the exact values to put in `filterConditions` (for example the real namespace names before filtering on `namespace`), or to answer "which clusters / accounts / resource types are there". The list is limited by the date range only: other filters do not narrow it. Paging: send `limit`; when the response has `nextCursor`, send it back as `after` for the next page. No `nextCursor` means the last page. Freemium customers (no paid Attribute plan) see network cost only, and only for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_workloads_resource_tag_keys1 of 8 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the distinct tag (label) keys found on cloud resources in a date range, sorted case-insensitively, one page at a time. Use `listAttributeWorkloadsResourceTagValues` to get the values of one key. The list covers every resource with tags in the date range, also resources no workload uses, and includes billing metadata labels such as `aws/currency`. Tags cannot be used in `filterConditions` yet: these lists are for information only. Paging: send `limit`; when the response has `nextCursor`, send it back as `after` for the next page. No `nextCursor` means the last page. Freemium customers (no paid Attribute plan) can only ask for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_workloads_resource_tag_values1 of 9 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the distinct values of one resource tag (label) key in a date range, sorted case-insensitively, one page at a time. Get the keys from `listAttributeWorkloadsResourceTagKeys`. The list covers every resource with that tag in the date range, also resources no workload uses. Tags cannot be used in `filterConditions` yet: these lists are for information only. Paging: send `limit`; when the response has `nextCursor`, send it back as `after` for the next page. No `nextCursor` means the last page. Freemium customers (no paid Attribute plan) can only ask for the last 60 days. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_attribution_sets1 of 4 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the customer's attributions (Attribution Center sets), sorted by name, one page at a time. Each set has its latest rule version in `rule`; `rule.state` is `etl-ready` for a published attribution and `ui-draft` for a draft. `activeRuleId` is the newest published version, or null when the set was never published. Deleted attributions are not listed. To get an attribution's cost over time or by value, run a Cloud Analytics report with `dataSource: attribution` and the dimension `attribution_tier_1` whose id is `attributionSetId` with `-` replaced by `_`. Only published attributions with data have cost. Paging: send `limit`; when the response has `nextCursor`, send it back as `after` for the next page. No `nextCursor` means the last page. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
count_attribute_attribution_sets1 of 2 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns how many attributions (Attribution Center sets) the customer has. Drafts count; deleted attributions do not. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
get_attribute_attribution_set1 of 3 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns one attribution (Attribution Center set) with its latest rule version. Get `attributionSetId` from `listAttributeAttributionSets`. An unknown or deleted set returns 404 `not_found`. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
list_attribute_attribution_set_versions1 of 5 parameters describedKubernetes workload cost data measured by the Attribute sensor, and the Attribution Center attributions that split cost into teams, products or customers. Returns the saved rule versions of one attribution, newest first, one page at a time. Drafts are included; discarded versions are not. Use it to see how an attribution's rules changed over time. Paging: send `limit`; when the response has `nextCursor`, send it back as `after` for the next page. No `nextCursor` means the last page. Authenticate with `Authorization: Bearer <token>`. Omit `X-Tenant-Id` when the credential resolves to one customer. When the credential can act on several customers, send `X-Tenant-Id: <tenant-id>` to select one.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.