An amendment that narrows past the market wins allowance and loses the value. ClaimHit maps the claims you are prosecuting against real products — and, for standards work, against the specification itself — so you can see where today's language actually lands before you decide how to narrow it.
Run the published application you are prosecuting and see which real products the current claims read on, element by element, each match backed by a citable source. The map you amend against — not a guess about the market.
For SEP prosecution, claims are mapped to the mandatory provisions of the technical standard, read from the specification text — 3GPP, ETSI, IEEE, ITU — rather than a summary, so an Office Action response can track what the standard actually requires.
The claim is decomposed into individual elements, each judged on its own evidence, so you can see exactly which limitation is doing the work — and which one a proposed amendment would put at risk.
Where the public record does not support a limitation it is reported NONE, never rounded up — so the map you steer amendments by reflects the evidence rather than optimism.
Candidates come from several models, live web and neural search, forward citations, and the authoritative registries for the field — but breadth only widens the net. Each one is still checked against real, citable evidence, and anything that cannot be evidenced is dropped rather than shown with a caveat. See every source →
ClaimHit shows where the claims on file read today; the amendment strategy stays yours. Run the application as it stands and see which products the current language still captures.
Apply for Beta Access →