---
title: "Quickstart - accept agent signups"
description: "The short path from a discovery document to a verified assertion and a signed receipt."
image: "https://docs.agentregistrar.dev/og/docs-default.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.agentregistrar.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart - accept agent signups

## Before you start

You need an HTTPS origin you control, the exact bytes of your terms of service, an Ed25519 keypair if you issue RP-signed receipts, and a place to store the account mapping.

## What a conformant provider does

A conformant provider does four things: serve an identity-only `/.well-known/agent-signup.json`, verify the assertion against the broker's JWKS with every check in section 7.1, return the stable error codes, and optionally return an RP-signed receipt plus a hash-pinned context guide. An optional provider account adds a broker-issued verification credential, authenticated receipts, abuse standing, and the verified listing; it is not required to accept assertions.

> **Before you publish**
>
> Discovery is identity-only. SKUs, endpoints, quotas and API usage belong in the post-signup guide, not in the discovery document. A document that advertises vendor capability fails conformance.

## Next

The step-by-step provider quickstart lives in the [Providers](/providers/) section. The normative implementation guide is [implementing-agent-identity-v1](https://github.com/agentregistrar/spec/blob/v1.2.0/implementing-agent-identity-v1.md), and the [validator](https://github.com/agentregistrar/spec/blob/v1.2.0/validator.md) checks a document before you publish it.

Source: https://docs.agentregistrar.dev/start/quickstart-provider/index.mdx