Legal research integration

The Hukuk connection is designed for searching Yargıtay, Danıştay, the Constitutional Court, UYAP precedent and regulator sources. Provides read-only research across official legal and regulatory sources. That means an assistant uses the permitted live-system context instead of guessing from a document. The result still depends on the freshness of the source system and the permissions granted to the connection.

A useful request makes clear which record is needed for which team. For this connection, a reliable flow is narrowing a question by case type, institution or date, then checking the returned source record before a decision. This makes filters and source records easier to inspect than asking for a broad list to be summarised.

results are not legal advice; the assistant retrieves sources while an authorised person owns interpretation and action. This is more than a technical detail: an incorrect action in a financial, customer, production or legal record can have real consequences. Reading a result and changing an external system are not the same level of authority.

Before rollout, decide which assistants and departments can see this data. If a result is unexpectedly broad, reduce the access scope; if data is absent, do not let the assistant invent the missing record. The underlying system record and the accountable owner remain the final check for every consequential result.

runs self-hosted on mcp-host with bearer authentication; queries are read-only and calls are metered in Kobi Credits. At setup, use a separate connection identity with least privilege so the accessible data does not exceed the operational need. For OAuth connections review the consent screen; for bearer connections review token scope, storage and ownership with the responsible team.

12 official sources and 0.1 Kobi Credits per call. This statement comes from the catalog or tool definition; no extra count is invented for a vendor-managed changing surface. During a pilot, observe real questions, returned records, confirmation steps and unnecessary calls. That evidence makes cost visible and exposes over-broad permissions early.