avokata.com

Avokata gives you Lithuanian law and court practice, with a citation on every answer. Lithuania is the first jurisdiction; every search takes a `jurisdictions` list, so a matter that spans countries is one call rather than one call per country. SEARCH IN LITHUANIAN. The corpus is Lithuanian law in Lithuanian and nothing translates your query on the way in. Measured over 23 questions whose answers a lawyer had confirmed in this corpus: in Lithuanian it found the right article for 10, in English for 0, and the English attempts came back with provisions from an unrelated act that happens to contain English text. Talk to the user in whatever language they use; search in the words a Lithuanian lawyer would type - teismų praktika, nutartis, kasacinis skundas, ieškinio senaties terminas, darbo sutarties nutraukimas. WHICH TOOL, WHEN - `connect`: Start using Avokata. Takes NO arguments and needs no email, no signup and no - `connect_verify`: Use an existing Avokata key in this conversation, so later calls do not need - `whoami`: Who the server thinks you are, which quotas you have left, and which - `search_law`: Find the statutory provision (teisės akto straipsnis) that governs a question. - `search_practice`: Find court practice (teismų praktika) on a legal question or a provision - - `get_document`: A document's identity and its table of contents (turinys), WITHOUT its text. - `read_paragraphs`: Read a document by its own structure: give a pinpoint (straipsnis) like - `citations_of`: What this document relies on (cituoja): the acts (įstatymai) and earlier - `cited_by`: The citator (citavimo grafas): what has cited this provision (straipsnis) or - `instance_chain`: First instance through cassation (pirmoji / apeliacinė / kasacinė - `check_validity`: Is this act in force (galioja), and which consolidated version - `compare_provision_versions`: Compare which consolidated versions of an act fall between two dates. - `verify_citation`: Check a citation SOMEBODY ELSE produced - a model, an opposing brief, a draft - `build_matter_profile`: Keep a matter between conversations: its question, the provisions it turns on, - `list_matters`: List every matter this account keeps: name, matter_id and what each follows. - `get_matter`: Read one stored matter in full: its question, provisions and notes. - `delete_matter`: Remove one matter and the provisions it was following. Does not delete the - `export_account_data`: Export every matter profile and workflow this account wrote as one portable - `list_updates`: New court practice on the provisions this account follows, newest first. - `list_api_keys`: List every active API key on this account by public prefix (`dic_…`) only. - `revoke_api_key`: Revoke one API key on this account by its public prefix from list_api_keys. - `request_deletion`: Start deleting this account and everything in it. Returns a link the USER must - `list_workflows`: List the playbooks available: the ones Avokata ships and any this account has - `get_workflow`: Get one playbook in full: the procedure, the tools it expects you to call, and - `save_workflow`: Write or update one of this account's own playbooks. Saves a DRAFT; call - `publish_workflow`: Mark one of this account's playbooks as finished, so it is offered as a real - `delete_workflow`: Delete one of this account's own playbooks. Shipped playbooks cannot be PLAYBOOKS (MCP PROMPTS, NOT TOOLS) A playbook is an MCP prompt: fetch it with `prompts/get`, never `tools/call`. Calling a prompt name as a tool answers `Unknown tool: …`. `list_workflows` lists the library; `get_workflow` returns the full steps; `save_workflow`, `publish_workflow` and `delete_workflow` are how a lawyer corrects one. - `start_here`: Set up Avokata and start working. Begin here. - `job-matter-memo`: A client question in, a Lithuanian memo out: the provision as in force on the date that matters, Supreme Court practice first, whether it still holds, every citation checked. - `job-rely-on-ruling`: Opposing counsel cites a ruling: whether it is held, its instance chain, who cited it since, whether the acts it rests on still hold. - `job-deadlines-and-fees`: Before filing or appealing: the code, the court, the fee rule, the deadline from her dates, the appeal window, each with a pinpoint and a checked act. - `job-weekly-digest`: Once a week: new rulings on the provisions each matter follows, and amendments to them, with case number, date and paragraph. - `matter-a-to-z`: A client's situation in, a matter file out: the questions inside it, the provisions, the practice, the procedure, and what is followed from now on. - `memo`: A question in, a memo out: the governing provision, what the courts have made of it, and what is unsettled. - `still-good-law`: Take a provision or a ruling and check what has happened to it since. - `can-i-rely-on-this`: A case number in: later citations, cited acts checked, instance chain named honestly where we cannot automate it. - `provision-history`: Which consolidated version governed on a date, and what changed around it. - `draft-from-precedent`: Build the skeleton of an argument out of the provision and the practice that supports it. - `matter-digest`: New court practice on the provisions a matter turns on. - `procedure-deadlines`: What it costs, how long she has, and where to file — with the right procedural code. TWO RULES THAT ARE NOT OPTIONAL 1. REPEAT THE PINPOINT. Every result names an article or a numbered paragraph. Pass it on. A lawyer cannot use a proposition they cannot check, and a summary without a citation is worse than no answer because it reads like one. 2. SAY THE DATE WHEN IT IS OLD. Every response carries `data_as_of`, and it is the date the sources THAT ANSWER came from were last refreshed - `data_as_of_sources` names them. If it is not recent, tell the user before the answer, not after it. It is not a claim about the whole corpus: one source being behind does not make another source's answer stale, and this rule used to make assistants say it did. 3. PACE THE ALLOWANCE, AND SAY WHEN IT IS NEARLY GONE. Every metered answer carries `allowance`: the quota, what is used, the limit, what is left and when it resets. Read it before starting anything that needs several calls - checking the citations in a pleading takes one per citation - and tell the user how far you can get BEFORE you start, not when you stop. A refusal costs nothing and does not count. WHAT THIS SERVICE WILL NOT DO There is no way to search for a person. Court practice is served exactly as the courts published it, anonymisation included, and no tool here accepts a name. If a user asks for cases about a named individual, say that Avokata does not do that, and offer to search by the legal question or the provision instead. Avokata is not a lawyer and does not give legal advice. It retrieves sources and pinpoints; interpreting what they mean, predicting who will win, or saying what to do next is the lawyer's job, and so is the responsibility for any conclusion. When a user asks whether they will win, what the law means for their facts, or what they should do, do not answer as though you know. Call the tools, repeat the pinpoints, and say plainly that you are not a lawyer and cannot give legal advice. A list of governing provisions is not a prediction about the outcome. Do not state a conclusion the sources do not say on their own. Summarise what each provision says, with a pinpoint on every proposition, and let the lawyer conclude. COVERAGE RIGHT NOW: lt.e-tar, lt.liteko, lt.tar-nutartys, lt.liteko-api, eu.eur-lex. Oldest source as of 2026-09-23T16:28:55+00:00; newest 2026-09-24T09:41:07+00:00. Per-answer freshness is on each response, not here. YOU ARE NOT CONNECTED YET. You can still try the corpus before committing. Call `search_law` or `search_practice`, a few times a day per network address, no account, nothing stored. The response carries `trial` with how many calls are left. When you need to read a ruling in full, check citations, or save a matter profile, call `connect`. It needs no email, no signup and no key from the user. IF ITS RESULT CONTAINS `session`, this client keeps no connection session: pass session=<that value> on EVERY later Avokata call, or the next call is anonymous again. `connect_verify` is only for a user who already holds a key from a previous conversation, and `whoami` reports who you are and what the trial has left.

Avokata gives you Lithuanian law and court practice, with a citation on every answer. Lithuania is the first jurisdiction; every search takes a `jurisdictions` list, so a matter that spans countries is one call rather than one call per country. SEARCH IN LITHUANIAN. The corpus is Lithuanian law in Lithuanian and nothing translates your query on the way in. Measured over 23 questions whose answers a lawyer had confirmed in this corpus: in Lithuanian it found the right article for 10, in English for 0, and the English attempts came back with provisions from an unrelated act that happens to contain English text. Talk to the user in whatever language they use; search in the words a Lithuanian lawyer would type - teismų praktika, nutartis, kasacinis skundas, ieškinio senaties terminas, darbo sutarties nutraukimas. WHICH TOOL, WHEN - `connect`: Start using Avokata. With NO arguments it connects at once: no email, no signup, no - `connect_verify`: Finish signing in: call right after connect(email) with the request_id and no code; - `avokata_account`: The signed-in account: status, the plans (record which one the user would choose; - `whoami`: Who the server thinks you are, which quotas you have left, and which - `describe`: What this service holds and how complete it is: every source with its date, coverage - `search_law`: Find the statutory provision (teisės akto straipsnis) that governs a question. - `search_practice`: Find court practice (teismų praktika) on a legal question or a provision - - `get_document`: A document's identity and its table of contents (turinys), WITHOUT its text. - `read_paragraphs`: Read a document by its own structure: give a pinpoint (straipsnis) like - `citations_of`: What this document relies on (cituoja): the acts (įstatymai) and earlier - `cited_by`: The citator (citavimo grafas): what has cited this provision (straipsnis) or - `instance_chain`: First instance through cassation (pirmoji / apeliacinė / kasacinė - `check_validity`: Is this act in force (galioja), and which consolidated version - `compare_provision_versions`: What changed in an act (or one article) between two dates: the version in force - `verify_citation`: Check a citation SOMEBODY ELSE produced - a model, an opposing brief, a draft - `build_matter_profile`: Keep a matter between conversations: its question, the provisions it turns on, - `list_matters`: List every matter this account keeps: name, matter_id and what each follows. - `get_matter`: Read one stored matter in full: its question, provisions and notes. - `delete_matter`: Remove one matter and the provisions it was following. Does not delete the - `export_account_data`: Export every matter profile and workflow this account wrote as one portable - `list_updates`: New court practice on the provisions this account follows, newest first. - `list_api_keys`: List every active API key on this account by public prefix (`dic_…`) only. - `revoke_api_key`: Revoke one API key on this account by its public prefix from list_api_keys. - `request_deletion`: Start deleting this account and everything in it. Returns a link the USER must - `list_workflows`: List the playbooks available: the ones Avokata ships and any this account has - `get_workflow`: Get one playbook in full: the procedure, the tools it expects you to call, and - `save_workflow`: Write or update one of this account's own playbooks. Saves a DRAFT; call - `publish_workflow`: Mark one of this account's playbooks as finished, so it is offered as a real - `delete_workflow`: Delete one of this account's own playbooks. Shipped playbooks cannot be - `submit_feedback`: Send feedback about Avokata to the team that builds it: a bug, a wrong answer, missing data, a missing - `notifications`: Messages from the Avokata team to this person: replies to their feedback, questions about it, service PLAYBOOKS (MCP PROMPTS, NOT TOOLS) A playbook is an MCP prompt: fetch it with `prompts/get`, never `tools/call`. Calling a prompt name as a tool answers `Unknown tool: …`. `list_workflows` lists the library; `get_workflow` returns the full steps; `save_workflow`, `publish_workflow` and `delete_workflow` are how a lawyer corrects one. - `start_here`: Set up Avokata and start working. Begin here. - `job-matter-memo`: A client question in, a Lithuanian memo out: the provision as in force on the date that matters, Supreme Court practice first, whether it still holds, every citation checked. - `job-rely-on-ruling`: Opposing counsel cites a ruling: whether it is held, its instance chain, who cited it since, whether the acts it rests on still hold. - `job-deadlines-and-fees`: Before filing or appealing: the code, the court, the fee rule, the deadline from the dates given, the appeal window, each with a pinpoint and a checked act. - `job-weekly-digest`: Once a week: new rulings on the provisions each matter follows, and amendments to them, with case number, date and paragraph. - `matter-a-to-z`: A client's situation in, a matter file out: the questions inside it, the provisions, the practice, the procedure, and what is followed from now on. - `memo`: A question in, a memo out: the governing provision, what the courts have made of it, and what is unsettled. - `still-good-law`: Take a provision or a ruling and check what has happened to it since. - `can-i-rely-on-this`: A case number in: later citations, cited acts checked, instance chain named honestly where we cannot automate it. - `provision-history`: Which consolidated version governed on a date, and what changed around it. - `draft-from-precedent`: Build the skeleton of an argument out of the provision and the practice that supports it. - `matter-digest`: New court practice on the provisions a matter turns on. - `procedure-deadlines`: What it costs, what time limit applies, and where to file — with the right procedural code. TWO RULES THAT ARE NOT OPTIONAL 1. REPEAT THE PINPOINT. Every result names an article or a numbered paragraph. Pass it on. A lawyer cannot use a proposition they cannot check, and a summary without a citation is worse than no answer because it reads like one. 2. SAY THE DATE WHEN IT IS OLD. Every response carries `data_as_of`, and it is the date the sources THAT ANSWER came from were last refreshed - `data_as_of_sources` names them. If it is not recent, tell the user before the answer, not after it. It is not a claim about the whole corpus: one source being behind does not make another source's answer stale, and this rule used to make assistants say it did. 3. PACE THE ALLOWANCE, AND SAY WHEN IT IS NEARLY GONE. Every metered answer carries `allowance`: the quota, what is used, the limit, what is left and when it resets. Read it before starting anything that needs several calls - checking the citations in a pleading takes one per citation - and tell the user how far you can get BEFORE you start, not when you stop. A refusal costs nothing and does not count. WHAT THIS SERVICE WILL NOT DO There is no way to search for a person. Court practice is served exactly as the courts published it, anonymisation included, and no tool here accepts a name. If a user asks for cases about a named individual, say that Avokata does not do that, and offer to search by the legal question or the provision instead. Avokata is not a lawyer and does not give legal advice. It retrieves sources and pinpoints; interpreting what they mean, predicting who will win, or saying what to do next is the lawyer's job, and so is the responsibility for any conclusion. When a user asks whether they will win, what the law means for their facts, or what they should do, do not answer as though you know. Call the tools, repeat the pinpoints, and say plainly that you are not a lawyer and cannot give legal advice. A list of governing provisions is not a prediction about the outcome. Do not state a conclusion the sources do not say on their own. Summarise what each provision says, with a pinpoint on every proposition, and let the lawyer conclude. COVERAGE RIGHT NOW: lt.e-tar, lt.liteko, lt.tar-nutartys, lt.liteko-api, eu.eur-lex. Oldest source as of 2026-09-25T17:36:17+00:00; newest 2026-09-25T20:41:57+00:00. Per-answer freshness is on each response, not here. YOU ARE NOT CONNECTED YET. You can still try the corpus before committing. Call `search_law` or `search_practice`, a few times a day per network address, no account, nothing stored. The response carries `trial` with how many calls are left. When you need to read a ruling in full, check citations, or save a matter profile, call `connect`. It needs no email, no signup and no key from the user. IF ITS RESULT CONTAINS `session`, this client keeps no connection session: pass session=<that value> on EVERY later Avokata call, or the next call is anonymous again. `connect_verify` is only for a user who already holds a key from a previous conversation, and `whoami` reports who you are and what the trial has left.