Opposition · USPTO

Opposition 91306088

OtherUSPTO

Opposition 91306088 at USPTO between Hangzhou DeepSeek Artificial Intelligence Co., Ltd. and Unorthodox Research & Development, LLC, over the mark DEEDSEEK, filed Mar 24, 2026. Status in the office record: other.

View DEEDSEEKGet this data via the API
Status
Other
Result
Other
Filed
Mar 24, 2026
Marks involved
5
Parties

Who is involved

The parties as named in the office record.

Opponent

Hangzhou DeepSeek Artificial Intelligence Co., Ltd.

Company trademarks
Respondent

Unorthodox Research & Development, LLC

Timeline

How the case has moved

Dates from the USPTO record and the DEEDSEEK filing.

  1. DEEDSEEK filed

    Application 99358810 filed at the USPTO.

  2. Opposition filed

    Hangzhou DeepSeek Artificial Intelligence Co., Ltd. started opposition 91306088 at USPTO against DEEDSEEK.
Marks

Marks involved

1 contested mark, 4 marks the challenger relies on.

MarkRoleApplicationOffice
DEEDSEEKContested99358810USPTO
DEEPSEEKRelied on99019883USPTO
DEEPSEEKRelied on99021618USPTO
DEEPSEEKRelied on99021619USPTO
DEEPSEEKRelied on99025382USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_58bc9a12-84c7-4598-aeb4-02900836449b
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_58bc9a12-84c7-4598-aeb4-02900836449b",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91306088",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-03-24",
  "parties": [
    {
      "name": "Hangzhou DeepSeek Artificial Intelligence Co., Ltd.",
      "role": "opponent"
    },
    {
      "name": "UNORTHODOX RESEARCH & DEVELOPMENT, LLC",
      "role": "respondent"
    }
  ]
}