# Chainlink CRE Connect
Source: https://docs.chain.link/crec
Last Updated: 2026-05-01

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

**Chainlink CRE Connect (CREC)** is the client-facing interface to the <a href="https://docs.chain.link/cre" target="_blank" rel="noopener noreferrer">Chainlink Runtime Environment</a>. It gives applications two capabilities:

- **Inbound** — subscribe to **verifiable on-chain events** signed end-to-end by a Chainlink Decentralized Oracle Network (DON), on every supported network.
- **Outbound** — submit **gas-less, account-abstracted operations** (atomic batches of EVM transactions) that the DON broadcasts on-chain through your Smart Account.

You sign with the keys you already have. CRE Connect handles event verification, gas, nonces, relayers, and the on-chain account.

> **NOTE: Beta — permissioned access**
>
> CRE Connect is currently in **private beta**. Your organization must be provisioned by Chainlink before you can use
> the product. See [Get Access](/crec/getting-started) for the onboarding flow.

## What you can build

| Capability              | What it gives you                                                                                                                                                                                                                                                                     |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Verifiable events**   | A stream of on-chain events signed by the DON using <a href="/architecture-overview/off-chain-reporting" target="_blank" rel="noopener noreferrer">Off-Chain Reporting (OCR)</a>, which your application can poll, decode, and re-verify locally against the on-chain DON signer set. |
| **Gas-less operations** | A single signed payload becomes one or more EVM transactions executed atomically by your Smart Account — with no gas, nonce, or relayer management on your end.                                                                                                                       |
| **Protocol extensions** | Pre-packaged, protocol-aware modules layered on top of CRE Connect. The first available is [DTA](/crec/extensions/dta).                                                                                                                                                               |

## Understand the model

Start with the [Architecture](/crec/concepts/architecture) overview, then read the concept pages for the resources that make up the product:

- [Channels](/crec/concepts/channels) — the top-level scoping unit.
- [Watchers](/crec/concepts/watchers) — how on-chain contracts are observed.
- [Verifiable Events](/crec/concepts/verifiable-events) and [Event Verification](/crec/concepts/event-verification) — how OCR signatures travel with every event.
- [Operations & Transactions](/crec/concepts/operations) and [EIP-712 Signing](/crec/concepts/eip712-signing) — how gas-less writes are authorized.
- [Smart Accounts](/crec/concepts/smart-accounts) and [Account Abstraction & Gas Sponsorship](/crec/concepts/account-abstraction) — the on-chain execution model.
- [Confidence Levels](/crec/concepts/confidence-levels) — finality and latency trade-offs.
- [Extensions](/crec/concepts/extensions) — protocol-specific modules.

## Get started

- [Get Access](/crec/getting-started) — request access to the private beta.
- [Extensions: DTA](/crec/extensions/dta) — the first available protocol extension.
- [Release Notes](/crec/release-notes) — current status and changes.