# Clients and state contexts

Clients and state contexts functions with exact signatures, examples, and catalog metadata.

Canonical HTML: <https://determica.com/docs/category/clients-and-state-contexts>

Create transports and CLIENT values. Pin a client to one block or restore retained execution state.

- [attach_transport](/docs/functions/attach_transport.md) — Attaches transport authority to a pinned or execution CLIENT so missing state can be fetched without changing the CLIENT's durable state identity.
- [client](/docs/functions/client.md) — Creates a live CLIENT from a TRANSPORT or restores retained execution state by execution ID. An optional expected chain ID rejects state from another chain.
- [client_context](/docs/functions/client_context.md) — Returns the state identity and hydration status carried by a CLIENT, including its kind, chain, block, chain profile, and identity hash.
- [http_transport](/docs/functions/http_transport.md) — Builds a TRANSPORT for an HTTP or HTTPS JSON-RPC endpoint. It records the endpoint, declared chain id, and request policy without contacting the provider.
- [pin](/docs/functions/pin.md) — Resolves a live CLIENT to one exact block and returns a pinned CLIENT for repeatable state reads. Pin by tag, number, hash, or a matching number/hash pair, with optional canonicality enforcement. Identical normalized requests using the same constructed live-CLIENT wrapper share one resolution within a SQL statement; separate client(transport) constructions resolve independently, and a later statement resolves the selector again.
- [rpc_call](/docs/functions/rpc_call.md) — Sends a low-level JSON-RPC request and returns the response's result value as JSON. Provider errors and transport failures are raised as SQL errors.
- [transport](/docs/functions/transport.md) — Builds a TRANSPORT containing type, url, and chain_id without contacting the endpoint. Unlike http_transport, it does not add a config object.