# TRANSPORT

JSON configuration for an HTTP or HTTPS JSON-RPC client. It contains type, url, and chain_id, plus an optional config object. The caller supplies chain_id; constructing a TRANSPORT does not call eth_chainId or verify the endpoint.

Canonical HTML: <https://determica.com/docs/types/transport>

- Family: Logical
- Physical type: JSON

JSON configuration for an HTTP or HTTPS JSON-RPC client. It contains type, url, and chain_id, plus an optional config object. The caller supplies chain_id; constructing a TRANSPORT does not call eth_chainId or verify the endpoint.

## Used by functions

### Accepted as input

- [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.

### Returned as output

- [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.
- [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.
