# Onboard to the CCIP indexer
Source: https://docs.chain.link/ccip/ccv-starter-kit/onboard-to-the-indexer
Last Updated: 2026-09-27

> For the complete documentation index, see [llms.txt](/llms.txt).

Onboarding registers your committee's aggregator endpoints with the CCIP indexer. Once you are onboarded, the
indexer reads your attestations and the default executor runs your messages automatically. It is optional,
because executing a message on the destination chain is permissionless and you can always execute your own; but
until you onboard, that is the only way your messages get executed, since nothing reads your aggregators for you
yet.

## Onboarding prerequisites

- Size the committee for production. An undersized committee, or one with no redundancy, is not onboarded;
  see [Scale to a committee](/ccip/ccv-starter-kit/how-to/scale-to-a-committee).
- Expose every aggregator read endpoint publicly, with no authentication: over TLS, on a stable hostname, with
  no API key and no IP allowlist. Standard WAF or DDoS protection is acceptable if it does not block legitimate
  public reads. Keep each endpoint responsive: the indexer reads with a 10-second per-request timeout and
  retries, so answer well under 10 seconds. The off-chain kit's
  [onboarding requirements](https://github.com/smartcontractkit/chainlink-ccv-starter-kit/blob/main/RUNBOOK.md#9-getting-onboarded-into-the-ccip-indexer)
  documentation has the full bar.
- Prove the committee by sending a message that requires your CCV and executing it yourself. For EVM, follow
  [Test your setup](/ccip/ccv-starter-kit/evm/test-your-setup). Repeat the execution against each aggregator
  endpoint you will register, not just one. The off-chain kit's
  [self-execution validation](https://github.com/smartcontractkit/chainlink-ccv-starter-kit/blob/main/RUNBOOK.md#94-validate-your-committee-by-self-executing-a-message)
  documentation walks through it.

## Request onboarding

Email clusersupport\@smartcontract.com with:

- a display name for your CCV, and optionally a logo URL,
- a website and a primary contact,
- your resolver address and the chains it is deployed on (the address is the same on every chain),
- every aggregator read endpoint URL in the committee.

Send the endpoint list again whenever you add or remove an aggregator. The indexer identifies each endpoint by
its hostname, so keep hostnames stable and re-register any that change. The off-chain kit's
[onboarding documentation](https://github.com/smartcontractkit/chainlink-ccv-starter-kit/blob/main/RUNBOOK.md#9-getting-onboarded-into-the-ccip-indexer)
has the full requirements, including the response times the indexer expects.

## After onboarding

The indexer reads your aggregators, the default executor runs your messages, and the public CCIP API reports
your verifier entry instead of `UNKNOWN`. Keep your aggregators reachable: the indexer retries each message for up to one hour, and if all of
your aggregators stay unreachable past that window, it stops and the default executor never runs those messages.
The attestations are still in your aggregators, so recover those messages the same way you tested: execute them
yourself.

> **CAUTION: Disclaimer**
>
> Support and maintenance of this CCV Starter Kit does not guarantee the security, availability, or operation of any
> deployment, which may vary depending on its configuration. The code in the CCV Starter Kit, including examples,
> templates, and starter kit components (the “Codebase”), and any code examples or deployment instructions in this
> documentation are provided “AS IS” and “AS AVAILABLE”, may not have been audited, and may omit checks, validations or
> error handling. You are solely responsible for reviewing, testing, auditing and securing any implementation before
> deploying it in a production environment. The security, availability, and operation of any deployment of the Codebase
> varies depending on its configuration. You should not rely on the Codebase or this documentation for production use
> without first conducting your own technical, engineering, and security review. Please review the Chainlink Foundation
> Terms of Service, which provide important information and disclosures. By accessing or using the CCV Starter Kit or
> this documentation, including when using the CCV Starter Kit to deploy or operate a CCV, you acknowledge and agree
> that your access to and use of the CCV Starter Kit and documentation is subject to the [Chainlink Foundation Terms of
> Service](https://chain.link/terms) (the “Terms of Service”), as amended from time to time. Nothing in this notice
> limits the permissions granted under the applicable software license for any code included in the CCV Starter Kit or
> this documentation.