company_cloud_spend next channel
Status: Modified (v2 migration;
hg_idremoved; snake_case params) This tool is on the privatenextMCP channel for allow-listed orgs. When promoted, this file moves tomcp-tools/company-cloud-spend.md.
Retrieve cloud vendor and technology service data for a specific company using the HG Insights v2 API. Provide company_domain (required). hg_id is not supported by this endpoint — use company_domain.
Integration required: hginsights_v2__data_api
Cache schema version: 3 (differs from base — stale cached payloads from the public channel will not be served)
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
company_domain | string | Required | — | The company domain to look up (e.g. 'cisco.com'). Protocol prefixes, leading www., and trailing paths are accepted and stripped automatically; case is normalized. |
product_list | string[] | Optional | [] | List of product/vendor names to filter results by. If empty, all detected vendors are returned. Server-side fuzzy matching (no client-side Fuse.js). |
limit | integer | Optional | 50 | Maximum number of technology_services entries to return (default: 50, max: 200). Ignored when full=true. |
vendors_per_service_limit | integer | Optional | 10 | Maximum vendors to include per service entry (default: 10, max: 50). The total vendor count across all services is also capped at 100. Ignored when full=true. |
fields | ("vendor_name" | "vendor_logo" | "first_seen")[] | Optional | — | Project each vendor row to this subset of fields. vendor_name is always included. Ignored when full=true. |
full | boolean | Optional | false | When true, return the full payload with no limit, no per-service vendor cap, no total-vendor budget, and no field projection. Use only when you genuinely need the unbounded payload — large accounts may exceed 90 KB. |
Response Format
{
"company": {
"name": "Cisco Systems",
"website": "cisco.com",
"logo": "https://…"
},
"traffic_distribution": {
"north_america_percent": 42,
"emea_percent": 28,
"asia_pacific_percent": 18,
"latin_america_percent": 7
},
"technology_services": [
{
"service_name": "Compute",
"vendors": [
{
"vendor_name": "AWS",
"vendor_logo": "https://…",
"first_seen": "2021-03-01"
}
]
}
]
}
Response fields
| Field | Meaning |
|---|---|
company.name | Company display name. |
company.website | Company website. |
company.logo | Company logo URL (null when unavailable). |
traffic_distribution | Geographic distribution of company's web traffic (may be null). Exactly four regions: north_america_percent, emea_percent, asia_pacific_percent, latin_america_percent. |
technology_services | Array of technology service categories. Each entry has service_name and vendors[]. |
vendors[].vendor_name | Vendor name (always present). |
vendors[].vendor_logo | Vendor logo URL (null when unavailable; omitted when projected away). |
vendors[].first_seen | Date when vendor was first detected (may be null; omitted when projected away). |
Example Usage
{
"tool": "company_cloud_spend",
"parameters": {
"company_domain": "cisco.com"
}
}
Filter for specific vendors:
{
"tool": "company_cloud_spend",
"parameters": {
"company_domain": "cisco.com",
"product_list": ["AWS", "Azure", "Google Cloud"]
}
}
Related Tools
company_spend— IT spend data by category (not cloud-specific).company_technographic— full technology stack including non-cloud products.company_ai_maturity— per-provider cloud intensity from the AI maturity model.
Changelog
2026-07-31 — Breaking: params and envelope fields renamed to snake_case
Availability: live on the private
nextMCP channel for allow-listed orgs. The public/api/mcpcontract is unchanged.
Breaking change — parameter and envelope field names
Before (on next) | After | |
|---|---|---|
| Domain identifier | companyDomain | company_domain |
| Product filter | productList | product_list |
| Vendor limit | vendorsPerServiceLimit | vendors_per_service_limit |
| Field enum values | "vendorName", "vendorLogo", "firstSeen" | "vendor_name", "vendor_logo", "first_seen" |
Output before:
{ "trafficDistribution": { "northAmericaPercent": 42 }, "technologyServices": [{ "serviceName": "Compute", "vendors": [{ "vendorName": "AWS" }] }] }
Output after:
{ "traffic_distribution": { "north_america_percent": 42 }, "technology_services": [{ "service_name": "Compute", "vendors": [{ "vendor_name": "AWS" }] }] }
Credit cost, required integration key (hginsights_v2__data_api), and tool semantics are unchanged.
2026-07-30 — Breaking: v2 migration, domain-only identifier, hginsights_v2 integration
Why this changed: this tool now calls the unified HG Insights v2 API (POST /v2/companies/cloud-spend) instead of the Intricately API directly.
Breaking changes
| Before | After | |
|---|---|---|
| Company identifier | companyDomain OR hg_id (one required) | company_domain only (required) |
hg_id param | Optional | Removed — not supported by v2 cloud-spend endpoint |
| Required integration | intricately | hginsights_v2__data_api |
productList filtering | Client-side Fuse.js fuzzy match | Server-side (v2 handles fuzzy matching) |
Stop sending hg_id — it is no longer accepted. Use company_domain instead. The intricately integration is no longer required; configure hginsights_v2__data_api instead.
What stayed the same: tool name, other param names (limit, fields, full), and default caps (50 services, 10 vendors per service, 100-vendor total budget — all now enforced server-side). full=true bypasses all caps.