This tracker collects patents that rank AI answers by accuracy, trace text back to its source, catch conflicting data, and block AI agents or code before they cause harm. The batch shows Big Tech treating AI mistakes as an engineering problem with layers of checks, not a single fix.
152 filings · tracking since May 2026 · latest Sep 2026 · updates weekly
based on all tracked filings in this watchlist · refreshes every week
This fight is over who controls what AI systems are allowed to say, do, and reveal, covering everything from stopping made-up answers to blocking hackers who try to manipulate AI into breaking its own rules.
IBM carries the most weight here by a wide margin, with its filings spread across catching AI lies, protecting private data, and building safety checks into the models themselves, while Google follows with a focus on verifying answers and blocking outside threats.
a dated entry each week this watchlist moves · older entries stay archived
Nvidia leads this week with four filings focused on finding where AI goes wrong and checking if its own answers are good. IBM and OpenAI add patents around stopping AI from lying and keeping data safe.
This week's filings center on AI systems that check their own work, from health advice to code to image captions. IBM leads with four filings, while OpenAI and Adobe each added two focused on catching errors before they reach users.
This week's two filings both focus on making AI more transparent and accurate: Google is working on helping AI tell apart questions that sound alike, while IBM is working on showing people exactly which parts of an image made its AI reach a decision. Google and IBM each added one filing.
This week's filings center on catching AI systems when they lie, leak private data, or get manipulated into breaking their own rules. IBM leads with the most filings, while Microsoft and Google add work on testing AI for weak spots and tracking privacy attacks.
This week's filings center on AI systems that check themselves before acting, from testing answers before speaking to catching bad outputs before they reach people. IBM leads with two filings, joined by Adobe, Microsoft, Nvidia, Google, Samsung, and Amazon.
counts from tracked filings · focus read from each company’s own filings
20 or more filings in the last 8 weeks · 6 to 19 · under 6
the fights inside the fight · each with its three newest filings · new filings join every week
IBM 8, Google 5, Samsung 3
Several companies are filing patents for systems where an AI reviews, scores, or rewrites its own output before a person ever sees it. Google, IBM, Salesforce, and Adobe are all pushing versions of this idea, from rewriting false answers to grading articles to catching broken logic.
IBM 8, Microsoft 6, Salesforce 5
A cluster of patents focuses on stopping dangerous or off-topic requests at the door, before any AI model processes them or any data moves. Salesforce, AMD, IBM, and Microsoft are all filing around this pre-filter idea.
IBM 2, Amazon 1, Sony 1
IBM, Amazon, Sony, and Salesforce are each filing patents around systems that measure whether an AI is treating different groups of people differently, and in some cases let users or developers see and fix the problem.
Salesforce 3, Google 3, Nvidia 1
Multiple companies are patenting ways to make AI show exactly where each piece of an answer came from, so users can check the work. Salesforce, Google, IBM, and Microsoft are the main players here.
Google 3, OpenAI 2, IBM 2
Rather than one AI checking itself, some patents describe a group of AI systems that evaluate each other, with votes or scores to reach a safer final answer. IBM, Nvidia, and Salesforce are filing in this space.
Nvidia 2, Qualcomm 2, IBM 1
Qualcomm and Samsung are filing patents around hardware, phones, and network devices that can detect when an on-device AI model is producing bad results and flag or report the problem.
IBM 3, Microsoft 2, Samsung 1
Detecting AI-generated voices, images and video, and spotting fake fingerprints or face scans, before they pass as real. Microsoft, IBM, Adobe and Samsung are filing.
IBM 5, Nvidia 2, Microsoft 1
Protecting the model itself: trapping thieves, feeding controlled noise, tracing corrupted training, catching attackers who manipulate the model, and stopping leaks of private training data. IBM and Microsoft lead it.
Salesforce 3, IBM 3, OpenAI 1
Permission systems for AI that acts on its own: security clearances, least-privilege access, plain-English access rules, dashboards to override an agent, and risk scores that stop a costly move. IBM, Microsoft, Salesforce and Sony have filed.
IBM 5, Google 1, Salesforce 1
Training an assistant to admit the answer is missing, flag its own uncertain replies, refuse unanswerable questions, or ask a question back. Google, IBM and Salesforce are the filers.
IBM 3, Microsoft 2, Nvidia 1
Scoring an AI reply by readability, by how far it drifts from the right concept, or by checking documents against each other. Microsoft, IBM and Disney have filed.
Microsoft describes bots that deliberately attack AI models to find security weak spots.
IBM patents a system that tricks its own chatbots into saying harmful things to expose flaws.
Microsoft patents a deepfake detector that checks whether the physics in a video makes sense.
Microsoft targets hackers who manipulate AI into revealing information it was told to hide.
every tracked filing, month by month · counts are USPTO pre-grant publications, one per publication number (an application, not a granted patent)
US 2026/0278268 A1
Within the guardrails race, most patents focus on blocking bad outputs. Salesforce's filing shifts upstream to the handoff problem: controlling what data one AI agent can request from another during routine work, not just what it can say afterward.
US 2026/0277936 A1
Automated pinpointing of failure points across the data pipeline reduces diagnosis time from hours to moments, letting engineers skip the guesswork about which processing stage corrupted results.
US 2026/0277966 A1
Keeping AI from leaking confidential documents to unauthorized employees. OpenAI's system filters search results by user permissions before the AI can see them.
US 2026/0278452 A1
If complete, this system would let AI catch its own pattern of errors before repeating them, moving beyond the current one-shot answer model where mistakes vanish into the next query.
US 2026/0278401 A1
Automated monitoring that flags performance drops and pinpoints root causes replaces manual log review, compressing detection time from days to real-time and closing the window where degraded outputs reach users.
US 2026/0278347 A1
Real-time confidence scoring lets the model flag low-certainty outputs before delivery, then use user corrections as immediate retraining data rather than letting false statements propagate undetected.
US 2026/0277980 A1
Weighting sources by author credentials rather than treating all documents equally. Addresses the problem that current retrieval systems can't distinguish expertise levels when pulling material for AI answers.
US 2026/0277972 A1
Automated grading of retrieval-augmented generation pipelines addresses the verification gap: these systems can now measure whether they're pulling the right source documents before generating answers, without requiring manual review of each result.
US 2026/0279337 A1
If audio AI systems can be stress-tested against subtle sound variations before deployment, defects hiding in edge cases become visible during development rather than in production.
US 2026/0268157 A1
If guardrails can detect and fix their own drift in real time, enterprises stop playing catch-up as language and threats evolve. IBM's system monitors live traffic to spot what its filters miss, then retrains itself without waiting for human review cycles.
US 2026/0267620 A1
Accountability in AI-generated code requires a complete audit trail. IBM's approach isolates the coding session in a secure container so every prompt, response, and human sign-off becomes cryptographically locked and reviewable later.
US 2026/0268064 A1
Verifying image captions piece by piece rather than as a whole unit reduces the odds that a fabricated detail slips through uncaught, improving the reliability of AI-generated descriptions before they reach users.
US 2026/0267835 A1
Catching garbage data before training starts means models won't bake in confidently wrong answers from the ground up, shifting the guardrails problem from post-deployment fixes to prevention.
US 2026/0267618 A1
A self-correcting training loop means fewer manual labels needed to fix edge-case bugs, letting deployed tools improve without constant human intervention.
US 2026/0268113 A1
Catching data rot at the cell level means anomalies can't hide in context. IBM's approach spots when individual values break the logical pattern their row creates, rather than flagging outliers by statistical distance alone.
US 2026/0270296 A1
Detecting voice and text spoofing requires learning each person's baseline communication patterns. IBM's system builds individual behavioral profiles to spot imposters mimicking trusted contacts.
US 2026/0268214 A1
As AI systems grow harder to audit from the outside, this filing shifts focus inward: embedding a second model to monitor another's reasoning process for deception or reward-hacking during execution, not after the fact.
US 2026/0268180 A1
Preventing hallucinations requires mapping how facts connect, not just finding matching text. Salesforce's dual-graph approach validates answers by cross-referencing semantic relationships within source documents.
US 2026/0268155 A1
Detecting when AI models exploit their training metrics rather than solving actual problems. OpenAI's approach uses a second AI to monitor the first one's reasoning process and catch gaming behavior before it reaches users.
US 2026/0268208 A1
Containing AI output within isolated compute environments rather than letting responses flow freely across infrastructure. Red Hat's approach uses virtualization to ensure sensitive model answers stay locked to controlled runtime boundaries.
US 2026/0268124 A1
If an AI can identify its own errors before output, users get answers they can actually trust instead of confident-sounding mistakes that feel authoritative.
US 2026/0269037 A1
Catching unsafe health advice before delivery. Samsung's two-step check flags risks for individual medical conditions that generic AI recommendations miss.
US 2026/0267621 A1
Catching garbage input before code runs means AI systems could stop executing requests that are malformed or hostile, moving the safety check upstream from runtime to the instruction phase itself.
US 2026/0259794 A1
Within the guardrails race, most efforts focus on catching bad outputs after the fact. This patent shifts upstream to the training phase itself, teaching models to distinguish between similar queries so they stop producing near-miss answers in the first place.
US 2026/0260446 A1
Pixel-level attribution maps let engineers verify whether object detection relied on relevant image features or noise, making audit trails concrete instead of opaque.
US 2026/0253129 A1
Knowing when to refuse a question solves the false-confidence problem at the gate, stopping out-of-scope queries before they reach the main model.
US 2026/0252685 A1
Detecting privacy attacks at query time rather than after breach means blocking inference attacks before attackers compile enough overlapping answers to reconstruct sensitive records. The system flags the attack pattern itself, not just individual queries.
US 2026/0252800 A1
Detecting contradictions across documents at scale requires sorting claims by agreement level, not just fact-checking them one by one.
US 2026/0252702 A1
Finding harmful outputs requires exhausting manual probing. Microsoft's filing automates the hunt by deploying AI agents designed specifically to generate adversarial inputs and expose model vulnerabilities before release.
US 2026/0252812 A1
Running answers through competitive peer review rather than a single model means users get ranked outputs instead of unverified confident text. Confirms the guard-rail race moving toward multi-model validation as the baseline check.
US 2026/0252721 A1
If an AI trained on mixed-clearance documents can be forced to reveal restricted info through clever prompts, this filing adds enforcement at the output gate: blocking answers based on whether the user holds access rights to the source material itself.
US 2026/0254832 A1
Connecting suspicious domains through their relationships rather than checking each in isolation, a shift toward mapping webs of threat signals instead of scoring them one at a time.
US 2026/0252707 A1
A system prompt that rewrites itself when it detects manipulation attempts would shift defense from reactive patching to continuous adaptation, moving the guardrails work from developer hands to the model itself.
US 2026/0252614 A1
If it works, lawyers reviewing AI summaries won't have to manually verify each claim against source documents. IBM's approach runs generated text through mathematical verification that flags sentences with no basis in the original material.
US 2026/0252798 A1
Catching invented contract clauses requires sorting fabrication types: IBM's system distinguishes between summaries that omit real content versus those that conjure false details, letting compliance teams flag the right fix faster.
US 2026/0252791 A1
If users can see exactly which source text backs each AI claim, contract review shifts from blind trust to verifiable citation. Adobe's filing maps the connection between answer and evidence.
US 2026/0252813 A1
If an AI's answers gradually become wrong without anyone noticing, the guardrail fails. IBM's patent detects this drift automatically, identifying which specific factors caused the degradation.
US 2026/0252949 A1
Filtering which borderline cases reach human reviewers cuts the cost of building reliable training data. Adobe's approach identifies examples most likely to confuse expert judges, routing only those for annotation.
US 2026/0252875 A1
Blocking unauthorized knowledge at the model level rather than post-generation. IBM's approach splits AI into role-gated expert modules, so restricted information never enters the answer pipeline in the first place.
US 2026/0253408 A1
Confidence scoring per task lets users know which results to rely on when a chip runs multiple recognition jobs simultaneously, rather than treating all outputs as equally trustworthy.
US 2026/0252706 A1
Finding safety gaps at scale means developers can patch filter vulnerabilities before they hit production, moving from reactive firefighting to proactive defense discovery.
US 2026/0252694 A1
Prompt injection detection requires filtering user input before it reaches the model. Microsoft's approach converts queries to numerical signatures, comparing them against known attack patterns to block malicious requests at the gate.
US 2026/0252802 A1
Detecting verbatim regurgitation from training data requires comparing model outputs against source documents. IBM's filing provides a measurement method where companies can now quantify how often their deployed models leak private training material.
US 2026/0245549 A1
Input filtering at the user end catches biased or misleading prompts before they reach the model, shrinking the window where bad data can shape AI output.
US 2026/0244715 A1
A permission layer that isolates likeness-generation inside a server Nvidia controls, rather than letting the model run on user devices where requests can't be screened beforehand.
US 2026/0244408 A1
Feeding real database schemas into the AI's generation process constrains it to reference only columns and tables that actually exist, cutting hallucinations at the source rather than catching them after the fact.
US 2026/0244896 A1
The guardrails race so far has focused on catching bad outputs after AI generates them. IBM's filing moves upstream: filtering poisoned training data before it reaches code generators, so benchmark scores stay honest.
US 2026/0244783 A1
The race so far has focused on output validation. This filing moves the checkpoint earlier: it intercepts data flows between tools before an AI agent sends sensitive information to the wrong destination.
US 2026/0244660 A1
Most voice assistants grab the first answer they find and read it back to you. Samsung's new patent describes a system that gathers answers from several different sources, scores each one for relevance, and only then writes a final reply.
US 2026/0245390 A1
The race so far has focused on catching AI outputs through source verification and conflict detection. Microsoft shifts the angle by embedding physics as a built-in consistency check, catching deepfakes where light and gravity betray the generator's failures.
US 2026/0244996 A1
Most AI systems fail silently when part of their infrastructure goes offline. IBM's new patent describes a way for an AI to notice it's working with incomplete information and only answer when it's confident enough to be trusted.
US 2026/0236719 A1
Verifying machine translations without human review requires the AI system itself to evaluate accuracy using structured context about original meaning, not just statistical confidence scores.
US 2026/0236580 A1
Real-time monitoring of a model's internal states during inference could shift enforcement from output screening to mid-computation detection, catching harmful paths before they materialize into user-facing text.
US 2026/0236470 A1
Detecting anomalous database queries before execution fills a gap in the guardrails race: existing validation checks syntax, not behavior. Salesforce's statistical profiling method catches requests that deviate from normal patterns even when technically valid.
US 2026/0236462 A1
Pre-screening documents for AI-readability lets companies spot which manuals will confuse their models before deployment, shifting the fix from post-hallucination cleanup to upstream document design.
US 2026/0236562 A1
Users deploying language models could catch statistical bias against specific groups before deployment, replacing manual audits with automated measurement against protected categories.
US 2026/0239054 A1
Embedded AI models can alert the network when their predictions start failing, letting the system catch model decay before it degrades service rather than waiting for user complaints or manual audits.
US 2026/0236717 A1
Prompt decomposition before model inference prevents cascading failures from multi-step instruction chains, moving guardrails upstream from model output to input processing.
US 2026/0236340 A1
A verification layer that runs parallel to task execution means AI systems catch nonsense output before it reaches users, reducing the need for external fact-checking infrastructure downstream.
US 2026/0238615 A1
Stopping malicious requests at the perimeter requires spotting patterns in legitimate-looking traffic. Salesforce's fingerprinting approach catches suspicious requests before they enter cloud infrastructure, shifting detection upstream.
US 2026/0230401 A1
Embedding validation checks directly into 5G network operations lets Samsung spot prediction failures in wireless signal routing before they degrade service, shifting from post-deployment discovery to real-time detection.
US 2026/0229248 A1
The race adds a detection layer for synthetic speech. Microsoft's multi-angle acoustic fingerprinting targets the specific vulnerability of voice-based fraud, where current listeners can't distinguish generated from real audio.
US 2026/0228439 A1
The timeline so far focuses on catching bad outputs after generation. This filing shifts upstream: vetting code candidates before any run at all.
US 2026/0228607 A1
Comparing AI output word-by-word against the original source documents catches fabrications before they leave the system, directly preventing false claims from reaching users of medical summaries, legal briefs, or other high-stakes documents.
US 2026/0228538 A1
The guardrails race so far has focused on catching bad outputs after they happen. Salesforce moves the checkpoint earlier, monitoring an AI's reasoning mid-generation to stop drift before the response reaches users.
US 2026/0228103 A1
Sending live CRM tasks to AI agents and scoring their output lets companies measure whether a specific agent can handle real customer service work before deploying it.
US 2026/0229012 A1
The race so far has focused on catching AI output after generation; this filing shifts to detecting synthetic media before it spreads, using dual verification rather than single-pathway analysis.
US 2026/0228214 A1
The guardrails race now includes peer review: IBM's filing shows multiple AI models voting on each response's safety rather than relying on a single filter, with flawed answers bouncing back for revision instead of blocking outright.
US 2026/0228220 A1
The guardrails race so far has focused on catching bad outputs after generation. This filing shifts the constraint upstream: injecting logical rules directly into the prediction layer so inconsistent answers never surface in the first place.
US 2026/0220384 A1
The guardrails race so far has focused on catching bad answers after they're generated. Adobe moves upstream: train models to actively disqualify wrong options during reasoning, so accuracy depends on elimination logic rather than presentation order.
US 2026/0220141 A1
The guardrails race so far has focused on catching bad outputs after they happen. This filing moves upstream to prevent the problem: training AI models to know their own boundaries and refuse out-of-scope questions before generating an answer.
US 2026/0220474 A1
A separate AI layer monitors agent outputs in real time, catching policy violations and factual errors before they reach users rather than discovering problems after deployment.
US 2026/0220548 A1
The race assumes one filter can't be trusted alone. Nvidia's answer: run text through multiple judges in parallel and boost confidence in whoever sounds most certain, letting uncertainty itself become a reliability signal.
US 2026/0214112 A1
Serving decoy models to suspected attackers limits what thieves can learn from probing queries, shifting the burden from perfect detection to poisoning the stolen weights themselves.
US 2026/0208041 A1
Users could prevent AI agents from straying into off-limits game zones by pre-defining action boundaries, shifting control enforcement from the system to the person deploying it.
US 2026/0212126 A1
The guardrails race so far has focused on catching wrong answers after they're generated. This filing shifts upstream: making the AI show its work during answer construction, so false claims become visible before a user sees them.
US 2026/0212045 A1
Explainable AI methods force models to surface which input variables drive each prediction, letting teams spot when proxies for protected attributes influence outputs without explicit programming.
US 2026/0211997 A1
Watching agent actions in real time prevents malicious code from executing through compromised tools. This pins down the verification layer that must sit between user intent and actual system changes.
US 2026/0211873 A1
The timeline's source-tracing layer gets concrete: forcing AI to output the specific document or database behind each claim, not just a general category of evidence.
US 2026/0212135 A1
The race has focused on blocking bad answers; this filing shifts toward showing where answers come from. Google's system matches AI output back to training sources and adds clickable links, making the origin visible rather than hidden.
US 2026/0211980 A1
Built-in fairness measurement during training rather than post-hoc audits shifts when bias gets caught, moving the detection problem upstream into the development workflow itself.
US 2026/0212230 A1
Logging each AI decision with plain-language explanations lets humans spot errors in real time before autonomous agents execute them, directly addressing the visibility gap in high-volume decision scenarios.
US 2026/0211996 A1
The guardrails race has focused on stopping bad outputs; this filing shifts upstream to restrict what an AI agent can access during execution, not after.
US 2026/0203340 A1
Grading answer quality beyond word-level matching lets systems catch subtle errors that break meaning, a medically wrong answer reads as grammatically correct to simple fact-checkers.
US 2026/0203614 A1
Extracting rules from policy documents leaves gaps when AI misses implicit constraints. IBM's filing adds a formal logic layer that detects which rules the initial extraction overlooked, filling blind spots that manual review alone would catch too slowly.
US 2026/0203527 A1
Users get a confidence score based on text quality instead of fact-checking, letting them filter unreliable answers before acting on them.
US 2026/0200479 A1
Detecting out-of-distribution objects requires a parallel verification layer that stops the main classifier from acting on uncertain identifications. Zoox's filing describes how to build that second system.
US 2026/0202914 A1
A safety filter between brain signals and external devices could expand the guardrails story beyond AI software into neural interfaces, where misread or hijacked commands pose direct physical risks rather than just data accuracy problems.
US 2026/0203594 A1
Users get real-time detection of poisoned inputs before corrupted data warps model behavior, shifting the guardrails race from post-hoc auditing to active filtering at the gate.
US 2026/0203555 A1
Shrinking human review from hundreds of test cases to a focused subset speeds up model selection, letting teams compare outputs where the models actually disagree rather than wading through consensus answers.
US 2026/0203572 A1
Letting models learn which facts matter before they answer cuts off the source of phantom data. That shifts guardrails from catching errors after the model speaks to preventing them during training.
US 2026/0203411 A1
Automating identity verification would let the guardrails system validate data sources at the handshake stage, catching spoofed or compromised systems before they feed false information into AI training or inference pipelines.
US 2026/0196219 A1
Imagine an app flashing you an ad and then immediately grabbing whatever the microphone picks up right after. Google has filed a patent for a system that catches exactly that pattern and shuts it down.
US 2026/0196142 A1
Biometric verification of instructor identity within immersive environments extends source authentication beyond text and voice into real-time avatar control, blocking impersonation in live educational sessions.
US 2026/0195541 A1
The race so far has focused on catching bad outputs after they happen. IBM moves upstream by building a system that manufactures failure cases during development, then uses them to inoculate the model against real attacks.
US 2026/0195306 A1
The race needs guardrails that work before output reaches users. IBM's filing proposes visual verification as a checkpoint: the chatbot generates an answer, then searches images to confirm it matches reality before responding or declining to answer.
US 2026/0195229 A1
The race needs ways to sort good output from bad without human review of every piece. IBM's geometry-based scoring lets quality control scale past what editors can manually check.
US 2026/0197245 A1
The watchlist so far has focused on catching AI errors after the fact. This filing shifts the burden upstream: phones become sensors that feed accuracy data back to network AI systems in real time, creating a feedback loop rather than a forensic audit.
US 2026/0195943 A1
Fingerprinting AI outputs by the artist names used in their prompts lets detection systems reverse-engineer which real person's work an algorithm copied, making style-theft traceable instead of invisible.
US 2026/0192824 A1
Filtering autonomous vehicle decisions through dual planning systems with safety veto catches errors neither approach alone would spot.
US 2026/0195594 A1
The race so far has focused on stopping bad outputs. IBM's filing shifts upstream: inject noise during processing itself so models can't retain private details users fed them, even if later compromised.
US 2026/0195548 A1
The guardrails race includes feedback loops now: Disney's filing shows an AI that grades its own output against a quality threshold and iterates until it passes, moving beyond single-pass translation into self-correction cycles.
US 2026/0197352 A1
The guardrails race includes speed traps: blocking harmful code matters little if the check itself becomes a bottleneck. Google's caching method removes that delay, letting security rules execute at browser load time without reconstruction costs.
US 2026/0195320 A1
Most AI chatbots give you one answer and move on, even when that answer rests on assumptions you never confirmed. IBM is patenting a system that makes the chatbot stop, highlight those assumptions, and ask you to verify them before it tries again.
US 2026/0195620 A1
Runtime verification of model identity catches substitution and drift before decisions propagate downstream, closing a gap where corrupted weights could contaminate high-stakes outputs without detection.
US 2026/0195425 A1
Embedding copyright metadata directly into images lets rights holders block 3D reconstruction at the model-generation stage, preventing unauthorized asset creation before it starts rather than after infringement occurs.
US 2026/0195234 A1
The race needs systematic ways to score AI outputs. IBM's approach uses a second AI running branching tests against the first, automating the evaluation layer itself rather than relying on human reviewers.
US 2026/0195476 A1
Real-time fact-checking before removal decisions cuts the risk of moderating content based on outdated training data, a gap the guardrails race has struggled to close as information changes faster than model retraining cycles.
US 2026/0195233 A1
Baseline detection through observation lets the agent distinguish routine from anomalous behavior, then escalates uncertain cases to human review instead of blocking or flagging everything without context.
US 2026/0195453 A1
The guardrails race needs detection that works across app ecosystems, not just inside single binaries. This filing shows how guilt-by-association patterns in code can flag threats isolation-based tools miss.
US 2026/0195098 A1
Comparing actual code against design specs catches a class of defects that static analysis and testing miss: when software works but deviates from its intended architecture, creating latent risk for future AI agents operating on that codebase.
US 2026/0189536 A1
Encrypting the prompt-to-cloud path at the chip level prevents the OS from inspecting what gets sent for safety screening, which solves the enforcement gap where local-first systems could bypass centralized content policies.
US 2026/0189558 A1
Preventing unauthorized data leaks between cooperating AI agents requires explicit permission gates. Microsoft's filing defines how to restrict which agents can access which datasets, blocking lateral movement within multi-agent systems.
US 2026/0188308 A1
The guardrails race includes systems that spot bias after deployment, but this filing reveals IBM automating the detection itself, the AI generates test cases to find its own blind spots rather than waiting for humans to catch them in the field.
US 2026/0186754 A1
The race so far has focused on catching AI errors after they happen. This filing shifts upstream: preventing harm by validating code vulnerabilities before deployment, then learning from each confirmation to improve future scans.
US 2026/0187993 A1
Synthetic training data that marks document sections as answerable or unanswerable teaches models to reject questions their source material cannot resolve, rather than generating plausible false answers.
US 2026/0187474 A1
The guardrails race so far has focused on source verification and data conflict detection. This filing pivots to a different gap: whether sponsored content actually delivers what users searched for, catching ad-page mismatches before they reach users.
US 2026/0186578 A1
Defaulting to lower-risk commands when sensor confidence drops lets devices avoid costly errors from misclassified gestures, directly addressing the accuracy problem that undermines safe AI agent operation.
US 2026/0187372 A1
Splitting documents into smaller, more precise chunks before indexing prevents the AI from pulling sentences stripped of their surrounding context, addressing the retrieval stage where misreads originate.
US 2026/0187524 A1
Automated pattern discovery fills the detection gap: the system identifies fraud variants the model was never trained on by spotting statistical outliers rather than relying on predefined rules, letting defenses evolve faster than new attack types emerge.
US 2026/0189557 A1
Encoding access rules in natural language instead of code lets non-technical staff set AI agent permissions without developer involvement, reducing the friction that currently forces organizations to choose between tight security and operational speed.
US 2026/0187379 A1
A structured knowledge base validates extracted events before output, directly blocking the conflicting-data problem where AI systems confidently report contradictory facts from different sources.
US 2026/0187488 A1
The race includes methods to validate threshold changes in live systems. This filing covers how to test new decision boundaries safely without disrupting production, a gap between current guardrail auditing and deployment.
US 2026/0179733 A1
AI that learns molecular behavior needs training data free of corrupted examples. Samsung's patent automates the detection and correction of bad training samples, removing a manual bottleneck that currently slows down chemistry simulations.
US 2026/0178472 A1
The guardrails race so far has focused on catching AI errors after output. Samsung shifts upstream by filtering corrupted training data before it reaches the model, preventing bad code pairs from poisoning the learning process itself.
US 2026/0179191 A1
Processing corrupted images in frequency domain rather than pixel space lets the AI learn damage patterns more efficiently, which supports the broader need for AI systems that catch and correct errors before output reaches users.
US 2026/0179382 A1
Robustness testing during training catches models that flip predictions when video frames degrade slightly, preventing failures in real-world conditions.
US 2026/0169977 A1
Users get AI that learns to spot fabricated details by being trained on deliberately corrupted summaries, turning the hallucination problem into training data. This moves guardrails from external filters to built-in error detection.
US 2026/0170067 A1
The guardrails race so far focuses on catching bad output after it happens. Salesforce shifts upstream by training AI to know its own limits and refuse questions it can't answer reliably.
US 2026/0169842 A1
Detecting integration errors in real time requires the AI to validate its own code before deployment, not after failures reach users.
US 2026/0170097 A1
Detecting when AI misuses company data requires knowing what normal use looks like first. IBM's system builds that baseline automatically, flagging deviations in real time.
US 2026/0169744 A1
A filtering layer that inspects generated code for hidden destructive commands catches a specific risk: AI output that appears legitimate but embeds instructions designed to damage or compromise systems during execution.
US 2026/0170027 A1
Samsung's approach filters corrupted training data by having the model itself judge which examples are reliable enough to learn from, reducing the poisoned-data problem that degrades accuracy downstream.
US 2026/0170415 A1
The guardrails race includes protecting biometric checks themselves. Samsung's filing shows how to generate synthetic fake scans for training, solving the scarcity of real forgeries that leaves AI detectors blind.
US 2026/0161743 A1
Judging whether AI outputs are trustworthy requires more than one evaluator's opinion. Google's approach layers specialized scorers for different quality dimensions, then synthesizes their verdicts into a final ranking.
US 2026/0161673 A1
A controlled database map forces the AI to anchor answers to real data rather than generate plausible-sounding figures, pushing guardrails from post-hoc filtering toward preventing hallucinations at the source.
US 2026/0161712 A1
Using specialized AIs for different domains reduces the chance that one general model will hallucinate or produce errors outside its training. The routing layer becomes a new point where outputs get evaluated before reaching users.
US 2026/0161893 A1
The guardrails race so far has focused on catching problems after the fact. Google's filing points toward prevention: using a second model to fix errors in real time, before flawed output ever reaches users.
US 2026/0154561 A1
A guardrail that checks whether a summary actually serves its purpose downstream, not just whether it reads well. This catches a gap where intermediate AI outputs can be polished yet useless for the next step in the pipeline.
US 2026/0154534 A1
The guardrails race so far has focused on catching bad outputs after they happen. Google's filing moves the checkpoint upstream: automated safety testing that runs continuously without waiting for real-world failures.
US 2026/0154578 A1
Detecting hallucinations mid-generation rather than after the fact shifts the guardrail approach from reactive correction to live intervention, potentially stopping false output before it fully forms.
US 2026/0154642 A1
A risk-scoring layer that estimates damage before an AI agent executes autonomous actions, letting guardrails reject high-stakes moves rather than just flag them after the fact.
US 2026/0148045 A1
Routing requests mid-generation lets systems swap to specialized models without wasting compute on wrong tools, solving the efficiency problem when a single model can't handle varied complexity.
US 2026/0148012 A1
When multiple AI agents generate conflicting instructions for the same model, merging them into a single coherent prompt prevents the downstream model from receiving contradictory directives that could degrade output quality or produce errors.
US 2026/0141406 A1
Automated monitoring lets companies revoke an AI agent's data access during live operation instead of discovering problems in post-deployment audits.
US 2026/0141261 A1
Within the guardrails race, this shifts enforcement from human review of logs to real-time AI monitoring that can shut down rogue agents mid-operation rather than catching problems after they happen.
US 2026/0140935 A1
Conflicting source documents in vector databases cause LLMs to give contradictory answers. IBM's system detects these conflicts before they enter the knowledge base, preventing confident wrong answers.
US 2026/0141053 A1
Running generated code in an isolated environment first, then rolling back if problems emerge, shifts the detection work from code review to runtime behavior, catching logic errors that static analysis misses.
US 2026/0134274 A1
Mixture-of-Experts routing lets each specialist model focus on one text source, improving accuracy in source attribution, a key step before blocking or flagging AI-generated content in production systems.
US 2026/0134223 A1
Users get complete answers instead of orphaned numbers: the system retrieves related database columns automatically, so an AI query about ESG governance scores now includes peer benchmarks and methodology instead of a lone figure that makes no sense.
US 2026/0134341 A1
The race has focused on ranking and blocking bad outputs; Red Hat's filing shifts toward keeping explanations current as training data evolves, a prerequisite for any guardrail that must justify itself over time.
US 2026/0134003 A1
Validating AI output quality requires running the same query multiple times and ranking results, a brute-force check against single-pass hallucinations that most systems currently skip.
They target concrete failure points: an AI giving a confidently wrong answer, generated text with no clear source, conflicting documents in a knowledge base, and AI-written code or agents that act on bad information. The filings from IBM, Red Hat, Google, and Salesforce each attack one piece of that chain rather than proposing one universal fix.
These are patent filings, which show research direction, not confirmed products. Companies patent far more systems than they ship, so a filing here means IBM, Google, Red Hat, or Salesforce is exploring the idea seriously enough to protect it, not that a feature is live in any product.
As companies deploy AI agents and generative models in real products, they run into the same failure modes: wrong answers, untraceable text, and code or agents that act before anyone checks them. IBM, Google, Red Hat, and Salesforce are each patenting their own version of a check on that process, which suggests the industry sees this as a shared problem, not one vendor's issue.
Watch for filings that connect these checks together, like a system that ranks an answer, traces its source, and blocks a bad action in one pipeline instead of three separate patents. Also watch which company starts patenting checks on other companies' AI outputs, since that would signal guardrails becoming a shared industry layer rather than an internal tool.
Want this weekly breakdown for a company we don't cover? Patentlyze Pro →