v1

latestOpenAPI 3.1.02026-07-2652038.3 KB

API v1

Knowledge

Query

Search verified knowledge and get back a structured list of matching entities. Same input as knowledge_search — natural language or Dot-Notation Syntax — only the output shape differs.

Returns a structured array of matching results plus entities. The input field is called "input" (not "query").

Dot-Notation Syntax lets you express filters and structure directly:

. navigates entity/topic → attribute → nested facet (e.g. companies.industry)
= != > < >= <= filter a facet
AND / OR combine multiple values of the same field (e.g. investors=A AND B, series=A OR B); chain different fields with .
order_by=field ASC|DESC and limit=N steer which results surface, not just their order
return(f1, f2, ...) projects the result to just those fields (always keep an identity field like name)
Clauses can appear in any order
Numeric fields may come back as approximate strings (e.g. "over 100M", "~206,753") — synthesize, don't treat as exact

Examples:

{"input": "Which biotech companies were founded after 2020?"}

{"input": "companies.industry=fintech.founded_year>=2020"}

{"input": "people.role=CEO.company.industry=AI"}

Use this when: You want a filtered, structured list of entities back. NOT for: A researched prose answer with citations — use knowledge_search instead (same input, different output). NOT for: Looking up one specific entity by name — use entity_search.

post/v1/knowledge/query

Request body

inputstring required

Natural language question or Dot-Notation Syntax (e.g. "companies.industry=fintech.founded_year>=2020"). Dot-Notation Syntax is not a strict grammar — there is no syntax to get wrong. An empty or fallback result means no match, not a syntax error.

return_entitiesboolean

Whether to return the entities identified in the query response.

Example request

{
  "input": "companies.industry=fintech.founded_year>=2020"
}

Response

Successful Response

resultsobject[] required

A list of structured results for the query. Shape and schema will be determined by the query.

Example response

{
  "entities": [
    {
      "entity_type": "Company",
      "id": "e2932ee7-7b57-42b7-8c58-cdfcdf56ceb5",
      "mentions": [
        "Amenitiz"
      ],
      "name": "Amenitiz"
    },
    {
      "entity_type": "Company",
      "id": "e843fc48-8339-4c99-a6e2-e7fb1cc738b1",
      "mentions": [
        "H2SITE"
      ],
      "name": "H2SITE"
    },
    {
      "entity_type": "Company",
      "id": "af3ff4b5-27a9-45d5-8c67-b656cb38e6b8",
      "mentions": [
        "Fracttal"
      ],
      "name": "Fracttal"
    }
  ],
  "results": [
    {
      "company": "Amenitiz",
      "funding_amount": "€38.9M",
      "round_type": "Series B",
      "sector": "Hospitality SaaS",
      "year": 2025
    },
    {
      "company": "H2SITE",
      "funding_amount": "€36M ($37.2M)",
      "round_type": "Series B",
      "sector": "Hydrogen Energy",
      "year": 2025
    },
    {
      "company": "Fracttal",
      "funding_amount": "€29.8M ($35M)",
      "round_type": "Series B",
      "sector": "AI Maintenance",
      "year": 2026
    }
  ]
}