# Public and private services

Service Usage lets you discover, enable, and manage both globally available
Google Cloud APIs and restricted custom APIs in your Google Cloud project. While
public services are visible to every consumer, private services built with
Cloud Endpoints require explicit access grants before you can list or call
them.

## Public APIs and services

Public APIs and services are globally visible across all Google Cloud
projects. Examples of public Google Cloud APIs and services include:

- [BigQuery](https://docs.cloud.google.com/bigquery)
- [Cloud Storage](https://docs.cloud.google.com/storage)
- [Cloud Monitoring](https://docs.cloud.google.com/monitoring)

You need the appropriate [Identity and Access Management](https://docs.cloud.google.com/iam) permissions to list or use public
APIs and services in a Google Cloud project. For example, to enable a service,
you need the `serviceusage.services.enable` permission. For a list of
permissions related to Service Usage and IAM roles
that contain them, see
[Service Usage roles and permissions](https://docs.cloud.google.com/iam/docs/roles-permissions/serviceusage.md.txt).

## Private APIs and services

Private services are
typically APIs implemented using [Cloud Endpoints](https://docs.cloud.google.com/endpoints) running in
another Google Cloud project. To discover or use private APIs and services,
you must first be granted access by a principal with the necessary
permissions. To learn how to grant access to enable Cloud Endpoints APIs from
a Google Cloud project, see the following pages for each of the respective
Cloud Endpoints API frameworks:

- [Controlling who can enable your API](https://docs.cloud.google.com/endpoints/docs/openapi/control-api-callers.md.txt) for the OpenAPI Specification.
- [Controlling who can enable your API](https://docs.cloud.google.com/endpoints/docs/frameworks/control-api-callers.md.txt) for Endpoints Frameworks.
- [Controlling who can enable your API](https://docs.cloud.google.com/endpoints/docs/grpc/control-api-callers.md.txt) for gRPC.

You must also have the appropriate IAM permissions to list or use
private APIs and services. For example, to call the
[`services.enable`](https://docs.cloud.google.com/service-usage/docs/reference/rest/v1/services/enable.md.txt)
method for a private service, the `servicemanagement.services.bind` permission
is required. For a list of permissions related to Service Usage and
IAM roles that contain them, see
[Service Usage roles and permissions](https://docs.cloud.google.com/iam/docs/roles-permissions/serviceusage.md.txt).

When you list available or enabled APIs and services in a Google Cloud project,
the results include any public and private APIs you have access to. To learn
more about listing enabled and available services in your
Google Cloud projects, see
[List services](https://docs.cloud.google.com/service-usage/docs/list-services.md.txt).