Get a single chain

Returns the ChainDescriptor for a single chain identified by its stable id (eth, polygon, sol, …), wrapped together with the chain's most recent metrics snapshot. Use it to render a single chain's detail page or to confirm a chain id is part of the catalogue before composing endpoint URLs.

The descriptor itself is public: if you know a chain's id you get its descriptor, regardless of authentication or scope. The catalogue is treated as marketing/discovery data — scope gating happens on the list endpoint and on the per-key endpoints surface, not here. The only reason this endpoint returns 404 is an unknown id.

The metrics block is best-effort. It carries the latest health snapshot when the metrics aggregator is wired in; if metrics are unavailable the field is null and the descriptor still returns 200. A chain's runtime health is expressed by metrics.status, a closed union — see Response fields.

scope_missing is a status, not an error. scope_missing is one of the values in the metrics.status union. It marks a chain as visible but permission-gated — your key does not hold the chain's required_scope — rather than hiding it. It describes permission, never upstream health (contrast degraded / down). For a key-specific view of which chains you can actually call, use GET /v1/keys/{id}/endpoints.

Path parameters

200 OK — the descriptor paired with the latest metrics snapshot:

When no metrics aggregator is configured, metrics is null:

{ "chain": { "id": "eth", "...": "..." }, "metrics": null }

The error envelope is { "error": "<code>" }.

See errors.md for the shared error envelope and conventions.

JavaScript (fetch)

const res = await fetch("https://api.triport.io/v1/chains/eth", {
  headers: { Authorization: `Bearer ${process.env.TRIPORT_API_KEY}` },
});
if (!res.ok) {
  const { error } = await res.json();      // e.g. "chain_not_found"
  throw new Error(error);
}
const { chain, metrics } = await res.json();
console.log(chain.name, metrics?.status ?? "no-metrics");

TypeScript SDK (@triport/sdk)

import { Triport } from "@triport/sdk";


const triport = new Triport({ apiKey: process.env.TRIPORT_API_KEY! });


const { chain, metrics } = await triport.chains.get("eth");
//    chain: ChainDescriptor, metrics: ChainMetrics | null
if (metrics && metrics.status === "scope_missing") {
  console.warn(`${chain.name}: key is missing scope ${chain.required_scope}`);
}

Python (triport-sdk)

from triport import Triport


triport = Triport(api_key=os.environ["TRIPORT_API_KEY"])


result = triport.chains.get("eth")
print(result.chain.name)
if result.metrics is not None:
    print(result.metrics.status, result.metrics.latency_p50_ms)

• Descriptor is public; metrics are best-effort. A known id always yields 200 with the descriptor; metrics may be null if the aggregator is not wired. Only an unknown id produces 404.
• Don't build URLs from protocols[].path. Those paths are internal backend routes. Get callable, key-scoped URLs from GET /v1/keys/{id}/endpoints.
• Related endpoints: GET /v1/chains (list / scope-filtered catalogue), GET /v1/chains/{id}/metrics (metrics only), GET /v1/chains/{id}/metrics/series (bucketed history), and GET /v1/chains/events (live SSE status + metric ticks).