Having the teams defined behind each API helps ensure that both product and engineering stakeholders can be contact, and informed as part of producing and consuming APIs. The team structure for enterprises will work differently, but the general concept of having a team defined as the owners of API will translate and be able to incorporated into each API contract.
Having a team definition, available as an artifact included in the contract, but then also additional references in platform infrastructure helps ensure there is an owner behind each API, is available for direct engagement, but also automation via source control, CI/CD pipelines, and other channels. The teams behind APIs should be governed alongside the technical details of each API they own.