pp-uspto-tsdr

Uspto Tsdr — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the uspto-tsdr-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install uspto-tsdr --cli-only
   

2. Verify: uspto-tsdr-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.5 or newer):

go install github.com/mvanhorn/printing-press-library/library/developer-tools/uspto-tsdr/cmd/uspto-tsdr-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

When Not to Use This CLI

Do not activate this CLI for requests that require creating, updating, deleting, publishing, commenting, upvoting, inviting, ordering, sending messages, booking, purchasing, or changing remote state. This printed CLI exposes read-only commands for inspection, export, sync, and analysis.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Trademark intelligence

• trademark status — Full current state of a trademark in one command — mark text, status, owner, classes, filing/registration dates, attorney, and prosecution event count

  Agents evaluating trademark status need the complete picture in one call instead of parsing XML manually

  uspto-tsdr-pp-cli trademark status 97123456 --json
  

• trademark timeline — Every prosecution event in chronological order — office actions, examiner reviews, publication events, and registration milestones

  Trademark attorneys need the full event history to evaluate prosecution strength and identify potential issues

  uspto-tsdr-pp-cli trademark timeline 97123456 --json
  

• trademark docs — List all documents in the prosecution file — office actions, responses, specimens, registration certificates — with type and date filtering

  Litigation prep and due diligence require reviewing every document in a trademark file without clicking through the TSDR web UI

  uspto-tsdr-pp-cli trademark docs 97123456 --filter-type SPE --json
  

Portfolio management

• trademark deadlines — Calculate Section 8, 9, and 15 maintenance deadlines with window-open dates and days-away countdown

  Missing a maintenance deadline means losing the registration — this is the #1 pain point for trademark portfolio managers

  uspto-tsdr-pp-cli trademark deadlines 97123456 --json
  

• trademark watch — Monitor multiple trademarks for status changes — caches previous statuses locally and flags any changes since last check

  Agents monitoring trademark portfolios need change detection, not full status dumps they have to diff themselves

  uspto-tsdr-pp-cli trademark watch 97123456 97654321 --json
  

• trademark batch — Batch status lookup for multiple trademarks using the multi-case endpoint or individual fallback with rate-limit throttling

  IP paralegals managing hundreds of marks need batch status without manually checking each one

  uspto-tsdr-pp-cli trademark batch 97123456 97654321 --json
  

HTTP Transport

This CLI uses Chrome-compatible HTTP transport for browser-facing endpoints. It does not require a resident browser process for normal API calls.

Command Reference

case-multi-status — Manage case multi status

• uspto-tsdr-pp-cli case-multi-status — Parameters can be one of the following: rnXXXXXXX for US registration number, snXXXXXXXX for US serial number,...

casedoc — Manage casedoc

casedocs — Manage casedocs

• uspto-tsdr-pp-cli casedocs get-bundle-info-pdf — Digits can be entered in one of the first four parameters. rnXXXXXXX for US registration number, snXXXXXXXX for US...
• uspto-tsdr-pp-cli casedocs get-bundle-info-xml — Digits can be entered in one of the first four parameters. rnXXXXXXX for US registration number, snXXXXXXXX for US...
• uspto-tsdr-pp-cli casedocs get-bundle-info-zip — Parameters can be one of the following: rnXXXXXXX for US registration number, snXXXXXXXX for US serial number,...

casestatus — Manage casestatus

raw-image — Manage raw image

• uspto-tsdr-pp-cli raw-image <serial_number> — Parameter is the digits only of the serial number, no leading sn. Example:...

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

uspto-tsdr-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Auth Setup

Set your API key via environment variable:

export TSDR_APIKEY_HEADER="<your-key>"

Or persist it in ~/.config/tsdr-pp-cli/config.toml.

Run uspto-tsdr-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  uspto-tsdr-pp-cli case-multi-status --ids example-value --agent --select id,name,status
  

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Read-only — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

uspto-tsdr-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
uspto-tsdr-pp-cli feedback --stdin < notes.txt
uspto-tsdr-pp-cli feedback list --json --limit 10

Entries are stored locally at ~/.uspto-tsdr-pp-cli/feedback.jsonl. They are never POSTed unless USPTO_TSDR_FEEDBACK_ENDPOINT is set AND either --send is passed or USPTO_TSDR_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

uspto-tsdr-pp-cli profile save briefing --json
uspto-tsdr-pp-cli --profile briefing case-multi-status --ids example-value
uspto-tsdr-pp-cli profile list --json
uspto-tsdr-pp-cli profile show briefing
uspto-tsdr-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Argument Parsing

Parse $ARGUMENTS:

1. Empty, help, or --help → show uspto-tsdr-pp-cli --help output
2. Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
3. Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:

claude mcp add uspto-tsdr-pp-mcp -- uspto-tsdr-pp-mcp

Verify: claude mcp list

Direct Use

1. Check if installed: which uspto-tsdr-pp-cli If not found, offer to install (see Prerequisites at the top of this skill).
2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
3. Execute with the --agent flag:

   uspto-tsdr-pp-cli <command> [subcommand] [args] --agent
   

4. If ambiguous, drill into subcommand help: uspto-tsdr-pp-cli <command> --help.