Bindings grant a Worker access to configured resources through its environment. Prefer a product's binding for supported operations inside Workers; use the REST API when the caller or operation requires it.

Read the relevant current documentation before implementing. These references route to maintained APIs and configuration rather than copying binding catalogs, type tables, or limits.

Start here

Bindings overview and catalog: capability model, available products, environment access, and binding lifecycle.
Storage options: choose storage from consistency, query, and coordination requirements.
api.md: environment access, generated types, and product APIs.
configuration.md: binding configuration, environments, secrets, and local development.
patterns.md: Worker-to-Worker calls, testing, and resource selection.
gotchas.md: missing bindings, stale clients, development differences, and limits.

Treat each binding as a capability granted to code. Select only the resources the Worker needs, and confirm which environment and resource each binding targets before using it.