docs: add links to api references

docs/README.md

@@ -76,7 +76,8 @@ better yet, a pull request.
     - [Figma resources](dls/figma.md)
   - API references
     - TypeScript API
-      - [Utilities](api/utility-apis.md)
+      - [Utility APIs](api/utility-apis.md)
+      - [Utility API References](reference/utility-apis/README.md)
       - [createPlugin](reference/createPlugin.md)
       - [createPlugin-feature-flags](reference/createPlugin-feature-flags.md)
       - [createPlugin-router](reference/createPlugin-router.md)

docs/api/utility-apis.md

@@ -19,7 +19,8 @@ during their entire life cycle.
 Each Utility API is tied to an `ApiRef` instance, which is a global singleton
 object without any additional state or functionality, its only purpose is to
 reference Utility APIs. `ApiRef`s are create using `createApiRef`, which is
-exported by `@backstage/core`. There are many predefined Utility APIs defined in
+exported by `@backstage/core`. There are many
+[predefined Utility APIs](../reference/utility-apis/README.md) defined in
 `@backstage/core`, and they're all exported with a name of the pattern
 `*ApiRef`, for example `errorApiRef`.
 

docs/auth/index.md

@@ -26,7 +26,8 @@ OAuth helps in that regard.
 
 The method with which frontend plugins request access to third party services is
 through [Utility APIs](../api/utility-apis.md) for each service provider. For a
-full list of providers, see [TODO](#TODO).
+full list of providers, see the
+[Utility API References](../reference/utility-apis/README.md).
 
 ### Identity - WIP