---
title: "Create an EvalGate account"
description: "Account requirements, social sign-in providers, payment policy, and post-signup API-key steps."
canonical: "https://www.evalgate.com/auth/sign-up"
last-updated: "2026-08-24"
---

# Create an EvalGate account

EvalGate production signup uses an interactive browser redirect with GitHub or Google. Choose one provider and approve the identity request. EvalGate does not ask for an email/password pair or send a separate EvalGate verification email. No payment card is required for the free allowance.

## What is required

- A GitHub or Google account that can complete the provider's sign-in and consent flow.
- JavaScript and an interactive browser for the person's social OAuth redirect.
- Acceptance of the EvalGate Terms of Service and Privacy Policy.

## After signup

1. Create or join an organization.
2. Connect a repository in Setup when using repository intelligence or CI.
3. Create a scoped API key under Developer → API Keys, or approve an agent-started credential handoff; either secret is shown once.
4. Add a separate model-provider key only for model-backed workflows.

## Agents without a browser

An agent can discover the RFC 8628 device grant at `/.well-known/oauth-authorization-server`, start with public client `evalgate-agent`, give the returned `verification_uri` and `user_code` to a person, then poll `/oauth/token` at the advertised interval. JSON-only clients can use `POST /api/agent-setup/start` and `POST /api/agent-setup/poll`. The person signs in with GitHub or Google, reviews the exact organization and scopes, and approves or denies the request. No API key is created before that approval. See the [agent credential handoff](https://www.evalgate.com/agent/setup.md).

- [Interactive signup](https://www.evalgate.com/auth/sign-up)
- [Authentication walkthrough](https://www.evalgate.com/auth.md)
- [Authentication docs](https://www.evalgate.com/docs/authentication)
- [Pricing](https://www.evalgate.com/pricing.md)