Eureka on the web
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →A 17-family dataset on multi-agent role assignment patents: no single filer tops the count, and China, India and the US lead filing offices.
17 published records collapse into 17 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 5 of 17 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.
This search looks for records combining role assignment or agent role language with multi-agent terminology and either collaboration or coordination in the title, abstract or claims. It returns 17 published records, which de-duplicate to 17 simple patent families, meaning each invention in this set was filed only once, without the duplication across countries that a family count elsewhere would need to collapse. The search string carries no date limit, so this is every matching record the database holds, not a window bounded by a start year.
At 17 families, this is a small pool. The figures below describe what this particular search returned, not the shape of a field or an industry, treat the page as a starting point for a deeper search in Patsnap Eureka rather than a finished map.
Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. 2 rows in this table start with the same name (VELLORE INST OF TECH CHENNAI, VELLORE INSITUTE OF TECH). They are left as separate rows, so the largest-filer figure above is per legal entity, not per group. Rows that look related still cannot be added together: one family can name several of them. Counted one by one, those rows between them cover more than the largest single row does, so the largest single row is not necessarily the largest filer in this field. How much those rows cover together is not something this dataset can say: one family can name several of them, so their counts cannot be added. Every ranking statement on this page is per individual filer row, never per group. Filings held by named individuals rather than organisations are removed where they can be identified (5 here); that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 16 of the 16 filers returned for this search; the data endpoint returns at most 100 entities, so even that 16 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.
Three views of the same 17-family dataset: where applications were received, how published records accumulate by filing year, and which IPC subclasses recur.
Published records run from 1 in 2020 to a peak of 8 in 2025, with 6 recorded for 2026 so far. Records from 2022 onward are still filling in as later-filed applications publish, so the most recent years understate the eventual count; no growth rate is shown because the series is too thin to read one reliably.
Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two.
G06N (computing based on AI models) appears on 64.7% of the 17 families, ahead of G06F (electric digital data processing) at 52.9% and G06Q (business, commerce & admin data processing) at 41.2%. H04L and H04W (digital information transmission and wireless networks) each sit at 17.6%. A family can carry several IPC classes, so these shares add to more than 100%.
Shares are the percentage of the 17 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.
This page is one run against one query. Ask Eureka your own question about multi-agent role assignment for collaborative task execution patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaA system and method are provided for automating software development documentation using multi-agent artificial intelligence. The disclosed systems and methods may include cloud-based infrastructure, an AI processing pipeline, and an integration framework. The system and method are automated to analyze code changes in real-time, generate appropriate documentation, and ensures accuracy through a novel verification process, resulting in significant time savings and improved consistency and fidelity in software development workflows.This is simply the first record the search returns under the database's default ordering, not the most cited, newest or broadest filing in the set. Its number, assignee and filing date are shown alongside this summary.


Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →When it has to run inside your own pipeline.
Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.
Browse MCP servers →Three figures worth checking before drawing any conclusion from this dataset.
The search returns 17 published records, and all 17 de-duplicate to 17 simple patent families. That means no invention in this set was filed in more than one jurisdiction within the data retrieved, which is itself a fact about coverage, not about significance.
1 618 Research & Development Pte Ltd is named on 1 of the 17 families (5.9%). The other 16 listed rows each hold 2 or fewer families, including 16 filers tied on 1 family apiece; rows are not summed here because one family can name several filers.
The 17 published records were filed across three receiving offices: China (8), India (6) and the United States (3). This counts where applications were filed, not where any filer is based, and the three figures sum to the 17-record total because each record is counted once per office.
At retrieval, 5 of the 17 records (29%) were granted and still in force. The rest sit in other states, pending, withdrawn, refused, lapsed, or not determinable, which are not broken out individually, so no single one of those categories can be sized from this page.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to multi-agent role assignment for collaborative task execution patent landscape, with the prior art for and against each one.
This page surfaces the shape of one search. Narrowing or widening the string, or reading full claim sets, is the next step for anyone acting on it.
An abstract or a family count cannot establish claim scope. Before concluding a design sits inside or outside any filing here, pull the granted claim set itself.
Open the record in EurekaAt 17 families, small wording changes in the search string can move records in or out of scope. Adjacent phrasing is worth testing before treating this set as complete.
Refine the search in EurekaRecords filed in 2022 and later are still publishing, so this pool will grow. Monitoring the same string going forward catches additions as they appear.
Set up monitoring in EurekaThis particular search returns 17 published records, which de-duplicate to 17 simple patent families, meaning every invention found here was captured once rather than across multiple filing jurisdictions. The search string has no date limit, so this is every matching record the database holds regardless of filing date, not a bounded time window. A different search string covering related phrasing could return a different count, so this figure describes the search, not an exhaustive census of the technology.
Among the 16 listed filers (organisations only; individual-inventor filings are excluded from the list but remain in the totals). Sixteen filers are tied with 1 family each, so there is no single filer with a higher count than the rest. Because one family can name several filers, the rows are not summed into a combined share anywhere on this page.
The 17 published records in this set were filed across three receiving offices: China (8 records), India (6 records) and the United States (3 records). This reflects where applications were filed, not where any applicant is based, the dataset carries no nationality or country-of-origin information for filers. These three figures sum to the full 17-record total because each record is counted once per office.
No growth rate is reported on this page because the filing-trend series is too thin and too recent to read a reliable trend from. Published records run from 1 in 2020 to a peak of 8 in 2025, with 6 recorded so far for 2026, but years from 2022 onward are still filling in as applications with publication delays appear, especially those entering national phase late. Any apparent rise or fall in the most recent years should be read as incomplete data rather than a real movement.
US20260186773A1, filed by Brendan Putek, describes a system for automating software development documentation using multi-agent artificial intelligence, including cloud-based infrastructure, an AI processing pipeline, and an automated verification process for analysing code changes and generating documentation. This summary is drawn from the published abstract only. Determining what the patent actually blocks requires reading its granted claims directly; an abstract and a family count cannot establish claim scope or freedom-to-operate.
Go past this page: query the whole multi-agent role assignment for collaborative task execution patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.
Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:
TAC:(("role assignment" OR "agent role") AND "multi-agent" AND (collaboration OR coordination))
Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (G06N) carries 64.7% of the patent families, so this search returned a classification-tight set.
What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 17 records and 17 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.
Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list (5 of them here). Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 16 of the 16 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 16 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included
Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-15.
Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (5 of 17). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka
Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level
Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.
Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.
Patent data carries limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.
Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.
The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.
Machine translation. Assignee and organisation names originally recorded in Chinese, Japanese or Korean have been rendered into English by an AI translation step so that the tables stay readable. These renderings are best-effort and may not match a company's registered English name; the original name is what the underlying patent record carries, and it is what any Eureka query launched from this page uses.
Help us improve
Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.
This page