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

# Introduction

> Integrate against the roll.codes hosted coordinator from your Solidity contract and receive random numbers through a callback.

roll.codes runs the coordinator infrastructure for you. As an integrator, you deploy your consumer contract, send requests to the hosted coordinator for your network, and handle the randomness callback in your own contract.

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    See the minimal request and callback flow you need to integrate against the hosted coordinator.
  </Card>

  <Card title="Coordinator reference" icon="file-text" href="/contracts/coordinator-reference">
    Keep the request function, fee call, and callback interface beside you while implementing.
  </Card>
</CardGroup>

<CardGroup cols={2}>
  <Card title="Integration pattern" icon="blocks" href="/contracts/integration-pattern">
    Copy a fuller consumer example with request storage and settlement guards.
  </Card>

  <Card title="How roll.codes works" icon="git-branch" href="/concepts/how-roll-codes-works">
    Understand how the hosted coordinator, request lifecycle, and callback delivery fit together.
  </Card>
</CardGroup>

## What you own

* your consumer contract
* the application state keyed by `requestId`
* the callback logic that settles the result

## What roll.codes owns

* the deployed coordinator contract for supported networks
* the off-chain fulfillment pipeline
* delivery of the random number to your callback

## Recommended order

<Steps>
  <Step title="Read the quickstart">
    Start with the minimal hosted-coordinator integration shape.
  </Step>

  <Step title="Copy the integration pattern">
    Adapt the example consumer to your own state and game or app logic.
  </Step>

  <Step title="Use the coordinator reference">
    Check the exact request and fee interfaces while you implement.
  </Step>

  <Step title="Harden the callback">
    Review callback security and troubleshooting before you ship.
  </Step>
</Steps>