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.
60 filings · tracking since May 2026 · latest Jul 2026 · updates automatically as new filings publish
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 storyline 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.
The filings in this storyline cluster around three problems: judging AI output for accuracy, tracing where generated text or answers came from, and stopping AI systems from acting on bad information. IBM's patents cover ranking multiple AI answers before showing one, tracing text through a mixture-of-experts network, catching conflicting documents in a vector database, and stopping AI-generated code from deleting data.
Red Hat's filing keeps explainability data current as the underlying model changes, so an explanation stays accurate instead of going stale. Salesforce patents let one AI agent monitor other agents for compliance violations and block them mid-deployment if they step out of line. Google's patents cover routing a task to the right model mid-generation, merging conflicting prompts from multiple agents, judging summaries by whether they help the reader, and running automated safety drills that fire test prompts at a model without a human in the loop.
Together the filings suggest that catching AI mistakes now takes several layers: a check on the answer, a check on where it came from, and a check on what happens after it acts. Readers should watch whether future filings extend this thinking to areas we have not seen yet, like enterprise deployment audits or cross-company standards, since each new entry keeps testing whether one company's checks can catch what another company's model misses.
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.
Which company should we read for you?
We track 17 companies here. Pro is the same weekly breakdown for any company you choose, delivered privately. Type a name and we'll scope it and send you a quote.