Adversarial patent-infringement evidence analysis. Give it a patent and an accused product; a prosecution brief and a defense brief are argued independently, then a neutral judge returns an honest verdict — with the element-by-element record behind it.
One structured answer per run, built to be acted on or challenged.
SUPPORTED, NOT SUPPORTED, or INCONCLUSIVE — plus the controlling reason. A negative or inconclusive result is a valid, common and useful outcome, especially for the defense.
The plaintiff and defendant positions on each claim element, and the defendant's strongest non-infringement or invalidity argument stated at full strength.
Every cited source can be opened and checked. No fabrication, and no inflated confidence scores standing in for evidence.
Assertion or defense — the analysis runs the same way.
Bring your own patent and your own accused product. Kcalbin runs third-party analyses only, on the patents and products the requester brings, and the service does not expose Kcalbin's own portfolio targets to anyone.
Similarity is never proof of claim practice. This is the operating rule of the whole system, not a disclaimer bolted on afterwards. A verdict reflects the openable record at the time of the run — it is screening and evidence analysis, not adjudicated infringement, and not legal advice.
Built for machines first. It is a live agent-to-agent endpoint with a published discovery card.
| Discovery card | kcalbin.com/.well-known/agent.json |
|---|---|
| Task endpoint | https://kcalbin.com/a2a/patent-sentinel — Bearer API key required |
| Health endpoint | https://kcalbin.com/a2a/patent-sentinel/health — open |
| Required input | patent_number, defendant_product, defendant_company; optional claim_numbers |
| Authentication | Bearer token issued with a subscription |
Calling the task endpoint without a key returns HTTP 401 by design. The health endpoint is open so a buyer's agent can confirm the service is up before subscribing.
Access is issued with a subscription. Tell us the volume you expect and whether you are working assertion-side or defense-side, and a key comes back with the price for that shape of use.
Request an API key