recipe-patent-landscapelisted

# Recipe: Patent Landscape Analysis Map the patent landscape for a technology area, identifying key players, trends, and gaps. Each database uses its own query syntax — see `flowleap-uspto` for the USPTO Lucene grammar. ## Steps ### Step 1: Define Search Scope ```bash flowleap patent build-query "<technology description>" --allow-external-processing flowleap uspto build-query "<technology description>" --allow-external-processing ``` Done when you have an EPO CQL query and a USPTO ODP query for the area. ### Step 2: Broad Patent Search ```bash flowleap --json patent search --query "<CQL from step 1>" --limit 50 flowleap --json uspto search --query "<recommended_query from step 1>" --limit 50 ``` If one office answers `provider_keys_required`, its patent-data key is missing: map the live office in full, label the landscape as covering that office only because of a missing key — never as the shape of the field — and ask for the free key at the end. `flowleap patstat` aggregates stay available keyless, but they are twice-yearly snapshot counts, not a substitute for live search. See `flowleap-keys`. Done when both databases have returned their result sets, or the gated office is named as an open missing-key gap. ### Step 3: Corpus Analytics ```bash # Filing trends by year, country and CPC breakdowns, top assignees flowleap --json analytics --keyword "<technology>" --date-from 2015-01-01 flowleap --json analytics --cpc <cpc-prefix> --country US --date-from 2020-01-01 ``