# Start building

Source: https://docs.graphops.xyz/get-started

Go from a new GraphOps account to one authenticated request, query, or stream. You need an email
address, or a Google or GitHub account when those sign-in options are available. If you have not
picked a service yet, [choose a data service](/choose-a-service) first.

_Your application sends requests with an organization API key that includes the services it uses. GraphOps runs the service against the network you choose, and usage draws credits from your organization's balance._

## Set up and send your first request

### Create or access an account \[#create-or-access-an-account]

[Create account](https://platform.graphops.xyz/auth/register)

[Sign in](https://platform.graphops.xyz/auth/start?mode=login)

Choose email or an available Google or GitHub option and complete any requested email verification.
Then create an organization or select one you already belong to. If a teammate invited you, sign in
with the invited email and accept the invitation instead of creating a new organization.

If you need help signing in or finding a verification email, see
[Secure your account](/platform/account-and-security).

### Check your credits \[#check-your-credits]

Open [Billing](https://platform.graphops.xyz/organizations/current/billing) to see
your organization's available credits and plan. Every service draws from this one balance. Choose
your monthly credits or buy a top-up if your workload needs more; see
[Billing and credits](/platform/billing-and-credits) for credit sources and current prices.

### Create an API key \[#create-an-api-key]

[Open API keys](https://platform.graphops.xyz/organizations/current/api-keys)

Choose the services you plan to use and give the key a label that names the workload, such as
`local-dev`. Copy the key when it is shown and store it in a secret manager or server-side runtime
configuration; it is not shown again.

### Run one quickstart \[#run-one-quickstart]

- [Make an RPC request](/rpc/getting-started): Read the latest Ethereum block number.

- [Query a Subgraph](/subgraphs/getting-started): Read indexed entities from an existing Subgraph.

- [Stream five blocks](/substreams/getting-started): Run a standard package through the Substreams CLI.

Each quickstart shows the expected result. An authentication error usually means the key is missing
from the request, formatted incorrectly, or does not include the service you called; the service's
troubleshooting page lists the checks.

Examples include the setup steps for each client and a note with the versions used for testing.
Use **Example project** to download the complete program with its dependency lockfiles. Set
`GRAPHOPS_API_KEY` to your API key before running it.

## Setup reminder emails

If setup pauses partway, GraphOps sends one reminder email for the step you have not finished:

* **Create your organization:** you verified your email but have not created or joined an
organization. Follow the link to create one, or ask a teammate to invite you.
* **Create your first API key:** your organization does not have an API key yet. The reminder goes
to an organization owner and links to API keys.
* **Make your first request:** your organization has an API key, but GraphOps has not recorded a
request from it yet. The reminder links to this guide's quickstarts. Requests can take a short
time to appear, so you can ignore it if you have already sent one.

Each reminder is sent at most once, and no reminder is sent for a step you have already finished.
These are one-time service emails about your setup, so they have no unsubscribe option.

## Next steps

* [Production readiness](/production-readiness): Review credentials, retries, observability, and recovery before launch.
* [API keys](/platform/api-keys): Create separate keys for each environment and plan rotation.
* [Team and roles](/platform/team-and-roles): Invite teammates with the access their work needs.
* [Usage and limits](/platform/usage-and-limits): See which workloads use your credits.