The info contact object provides you with the ability to define a person, team, or other type of contact as name, email, and URL. The contact information should reflect the overall support strategy for an API, but also reflect the portable nature of an OpenAPI, and having the contact name, email, and URL as part of the information object in an OpenAPI is standard.
I recommend making sure that the name, email, and URL are all present, and it shouldn’t be an individual, unless you have a single person who is the face of a domain, line of business, or team. It is easy to make sure that your email and URL will all end up in the same place, and try to make the name best represent who is responsible for supporting an API.