Contract
{
"type": "object",
"required": [
"company_slug"
],
"properties": {
"company_slug": {
"type": "string",
"description": "Company slug identifier (e.g. 'google', 'meta', 'amazon'). Obtain from get_popular_companies."
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {
"overview": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"ticker": {
"type": "string"
},
"country": {
"type": "object",
"properties": {
"code": {
"type": "string"
},
"name": {
"type": "string"
}
},
"additionalProperties": true
},
"hq_city": {
"type": "string"
},
"website": {
"type": "string"
},
"hq_state": {
"type": "string"
},
"industry": {
"type": "string"
},
"insights": {
"type": "array",
"items": {
"type": "object",
"properties": {
"icon": {
"type": "string"
},
"insight": {
"type": "string"
}
},
"additionalProperties": true
},
"description": "Array of highlighted insights. The upstream provider itself returns null when it has none for this company (observed null on the real 'google' calibration call), but `responseShaping`'s field-map allowlist (`applyFieldMap`, `providers/omnial/hooks.ts`) treats a null at this array-typed allowlist node as 'omit the key entirely' -- so the document this tool actually hands back to a customer has NO `insights` key at all in that case, never `insights: null`. Do not rely on this key being present in the response; check for its absence to detect 'no insights', not for a null value."
},
"emp_count": {
"type": "number"
},
"description": {
"type": "string"
},
"company_type": {
"type": "string"
},
"vesting_type": {
"type": "string"
},
"year_founded": {
"type": "number"
},
"vesting_schedule": {
"type": "string"
},
"employee_count_range": {
"type": "string"
},
"estimated_annual_revenue": {
"type": "string"
}
},
"additionalProperties": true
},
"job_families": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"slug": {
"type": "string"
},
"category": {
"type": "string"
},
"description": {
"type": "string"
}
},
"additionalProperties": true
}
},
"related_companies": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"slug": {
"type": "string"
}
},
"additionalProperties": true
}
}
},
"additionalProperties": true
},
"status": {
"type": "string"
}
},
"description": "The company overview record, as returned at routing.responseResultPath ($.output).",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.01365 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 8, 2026