# Integrations & runtimes

An integration connects a particular capability. A provider logo or a catalog entry does not mean that every API, deployment destination or paid feature is configured for your project. Choose only what the project needs and check the connection's own status.

## AI connections

The browser creator supports personal API connections and separate native subscription workflows. Select the provider/model and the available route in **Connect AI**. Requests use that route's permissions and usage rules. EoC does not silently switch a failed subscription flow to a paid personal API connection.

Optional image generation needs its own supported OpenAI access and explicit enablement. Local PixelLab/Meshy workflows remain separate. See [AI connections](/docs/api-keys) and [artwork and audio](/docs/assets-and-audio).

## Game runtimes and tools

| Path | Role | Setup boundary |
| --- | --- | --- |
| Canvas / Three.js | Browser gameplay and previews | Use supported project source, assets and exports |
| Hosted project terminal | A separate command environment for development | Follow account access and provider-client setup |
| Local Companion | Connect an already configured computer to a supported native workflow | Public signed installer availability is listed separately |
| GEngine | AI-connected tools inside Unreal Editor | Compatible editor, plugin source/access and C++ toolchain |
| Multiplayer source editions | Server and game foundations you can adapt | Configure, host and validate the backend yourself |

Project MCP tools need an explicit project selection and a task that requires them. Resource documentation alone does not authorize a tool to execute or grant a service permission.

## Market data and blockchain examples

[Oracle Arena](/examples/chainlink) uses read-only Chainlink price data and historical practice challenges. Its source is available from the example. It does not require a wallet or place trades.

The [DEXPIT launch prototype](/examples/dexpit-launch) explores RWA card packs and a DEXPIT/GOLD launch curve. It reads supported Chainlink feeds on Robinhood Chain. Payments, asset acquisition, custody, issuance and randomness in this prototype are simulated. GOLD and GLD have separate roles; the prototype establishes no new redemption right or guaranteed return.

[Managed Birdeye](/docs/birdeye-integration) supplies supported read-only SOL/USDC price information to eligible accounts. It is not a trading or settlement service.

Optional EVM and Solana source modules demonstrate project-revision records. They are separate implementations that require deployment setup; selecting one does not migrate a game, custody funds or execute its rules onchain.

## Hosting and publishing

A public EoC play link, a source export, a cloud workspace release and an external-store kit are different destinations. Each needs its own appropriate source, configuration and rights. Exporting does not automatically provision a domain, multiplayer backend or store account.

Follow [publishing and export](/docs/publishing-and-export) for browser games and [store publishing](/docs/store-publishing) for native release preparation. Check [product status](/docs/product-status) before planning around an announced or limited-access capability.