get_organization
A public registry organization by ref, or by an external id (wikidata:Q95, lei:…, ror:…, cik:…, ein:…, domain:stripe.com), summary first: its identifiers (ids) and the parts of the business with counts and coverage, each with a handle. node=part:<key>, prim:<key>, comp:<id>, val:<id> drill down one level per call (val:<id> is one fact with its source); node=sec:links lists its connections (funded by, funds, parents, subsidiaries, each with the source of the link; rel:funded_by one relation); node=sec:sources lists the sources its facts rest on, each with the facts it supports. depth expands more at once; fields picks keys (fields=values, fields=sources). What it returns follows the profile page: without a key, names, values and sources below the primitives are withheld. view=v1 returns the whole public map.
Parameters
- refstringrequired
Registry ref, e.g. acme-builders-3f2a9c1d (from search or list_organizations), or an external id: wikidata:Q95 (or Q95), lei:…, ror:…, cik:…, ein:…, swatch:…, uei:…, dotgov:…, eutr:…, openalex:…, domain:stripe.com
min 3 charsmax 200 chars - depthnumberoptional
Levels to expand below the node, 0-4 (default 1)
≥ 0≤ 4 - nodestringoptional
Handle to expand, from an earlier response: part:hiring, prim:payroll, comp:3f2a9c1d
max 200 chars - fieldsstringoptional
Keys to keep per item, comma-separated; aliases values, sources, counts, confidence
max 300 chars - limitnumberoptional
Items per response, 1-200 (the budget may stop earlier)
≥ 1≤ 200 - cursorstringoptional
next_cursor from the previous response
max 2000 chars - viewenumoptional
compact (default), full (every field) or v1 (the old shape, unpaged, refused over 64 KB)
compactfullv1 - budgetnumberoptional
Token budget, 200-8000 (default 2000, 6000 for full)
≥ 200≤ 8000
Example call
Agents call tools by name; you rarely write this by hand. It is here so you can test the server from a shell or your own code.
{
"name": "get_organization",
"arguments": {
"ref": "acme-builders-3f2a9c1d",
"node": "prim:estimating",
"depth": 2
}
}Response
The result is one text content block holding this JSON (abbreviated here). Errors come back with isError: true and a message such as Error 401: … or Invalid input: ….
{
"node": {
"h": "prim:estimating",
"l": "Estimating",
"layer": "process",
"n": {
"comps": 1,
"vals": 2
}
},
"items": [
{
"h": "comp:3f2a9c1d",
"l": "In-house estimating team",
"layer": "people",
"conf": "inferred_high",
"n": {
"vals": 2
},
"items": [
{
"h": "val:9c2d41aa",
"l": "Estimating method",
"p": "estimating_method",
"v": "estimating software",
"s": 0
}
]
}
],
"src": [
[
"https://acmebuilders.example/careers/estimator",
"Estimator job post"
]
],
"hint": "Call get_organization ref=acme-builders-3f2a9c1d with node=comp:3f2a9c1d for its 2 values and sub-components.",
"tokens": 210
}Over REST
The same call without MCP: GET/api/v1/orgs/:ref