search
Search System Atlas: registry companies (name, domain, industry, coverage, claimed), industries and segments, primitives of published schemas, constructs and glossary terms; with a key also your workspaces, companies and components. Typo-tolerant and ranked. Filters can be written in the query (industry:staffing region:US layer:software type:company,primitive claimed:yes) or passed as parameters.
Parameters
- querystringrequired
Free words, optionally with filters, e.g. 'payroll industry:staffing'
min 1 charmax 200 chars - typestringoptional
Comma-separated: company, registry, my_company, industry, primitive, construct, glossary, workspace, component, mine
- industrystringoptional
Industry or segment key or name, e.g. staffing; includes its segments
- regionstringoptional
Region word, e.g. US
- layerenumoptionalpeopleprocesssoftwaredatadecisions
- claimedbooleanoptional
Only companies that mapped themselves (true) or not (false)
- sortenumoptionalrelevancecoverageupdated
- pagenumberoptional≥ 1≤ 1000
- limitnumberoptional
Hits per page, default 20
≥ 1≤ 50
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": "search",
"arguments": {
"query": "payroll"
}
}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: ….
[
{
"kind": "primitive",
"title": "Payroll",
"detail": "Paying workers on time and correctly.",
"industry": "staffing"
}
]Over REST
The same call without MCP: GET/api/v1/search