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

# Overview

> How demand partners integrate with CloudX and when the CloudX SDK renders your creative

CloudX connects demand partners to publisher inventory through the CloudX exchange over OpenRTB. Depending on your integration model, winning creatives are rendered either by your own network SDK or directly by CloudX.

## Integration models

<CardGroup cols={2}>
  <Card title="SDK bidder">
    Your network SDK is embedded in the publisher app via a CloudX adapter. Your SDK loads and renders the creative; CloudX orchestrates the auction and lifecycle. CloudX does not render it.
  </Card>

  <Card title="Server-to-server (SDK-less)">
    You respond to CloudX bid requests over OpenRTB with creative markup in `bid.adm`. There is no network SDK in the app — CloudX renders the creative directly. This is the path the [Creative Specification](/en/demand/renderer-spec) governs.
  </Card>
</CardGroup>

## When CloudX renders your creative

For server-to-server demand, a bid is rendered by the CloudX SDK when the bid response carries the render provider marker:

```json theme={null}
{
  "ext": {
    "cloudx": {
      "render": { "provider": "cloudx" }
    }
  }
}
```

When `provider` is `cloudx`, the CloudX SDK renders the creative in-app from `bid.adm`, regardless of which demand partner supplied the bid. When the marker is absent, rendering is delegated to a network SDK.

<Note>
  If your creatives are rendered by CloudX, read the [Creative Specification](/en/demand/renderer-spec) for the accepted creative types, supported formats, per-bid configuration, and user-experience behavior.
</Note>

## Getting started

Server-to-server integrations are provisioned per partner (bid endpoint, credentials, and creative review). Contact your CloudX partner manager to begin an integration.