Skip to content
DocsChartsNetworkLast updated Nov 2, 2026

Network

One hub and what it connects to. Sample data: one agent on Atlas 3 and its six tools, search 12.4K calls (32%), files 2.7K (7%).

Open in
Agent tool callsTool calls by the Atlas 3 agent this week across 6 tools: Search leads with 12.4K (32%), Files is lowest with 2.7K.AGENTAtlas 3Search12.4K · 32%Code run8.1K · 21%Browser6.2K · 16%SQL5.6K · 15%Email3.4K · 9%Files2.7K · 7%
Agent tool calls
ToolCallsShare
Search12.4K32%
Code run8.1K21%
Browser6.2K16%
SQL5.6K15%
Email3.4K9%
Files2.7K7%
Agent tool callsTool calls by the Atlas 3 agent this week across 6 tools: Search leads with 12.4K (32%), Files is lowest with 2.7K.AGENTAtlas 3Search12.4K · 32%Code run8.1K · 21%Browser6.2K · 16%SQL5.6K · 15%Email3.4K · 9%Files2.7K · 7%
Agent tool calls
ToolCallsShare
Search12.4K32%
Code run8.1K21%
Browser6.2K16%
SQL5.6K15%
Email3.4K9%
Files2.7K7%

Installation

  1. 1

    Set up the registry once

    This chart is free in Hearth and MIT licensed: no token. Add @chartory to components.json once (the URL alone, no headers), or skip this when another chart is already installed.

    Installation guide
  2. 2

    Add the chart

    One command adds the Network component to your project.

    npx shadcn add @chartory/network
  3. 3

    Use it

    Pass your rows. The props are the Figma properties.

    usage.tsx
    import { Network }  from "@/components/chartory/network"<Network  data={agentTools}  size="m"/>

Props

<Network>

Every prop but data is a Figma property with the same name and values.

PropTypeDefault
data: The chart's data. The tables below list every field.NetworkDataRequired
size: The size class. Each one is laid out again from the data."xs" | "s" | "m" | "l""m"
color: The data colour of the primary marks (data/primary)."cat-1" | "cat-2" | "cat-3" | "cat-4""cat-1"

NetworkData

The data prop: one object for the whole chart.

PropTypeDefault
hub: The hub's label.stringRequired
hubSub: The line under the hub's label.stringRequired
nodes: One entry per node.NetworkNode[]Required

NetworkNode

One object per entry in nodes.

PropTypeDefault
label: The name shown on the chart.stringRequired
v: The value.numberRequired
tok: The colour token, e.g. "data/primary".stringRequired
text: The label as shown.stringRequired
subs?: The sub-values.number[]—

The data as a JSON Schema: schemas/network.json

Network chart: a React and Figma chart in four sizes

What does a network chart show?

A network chart draws items as nodes and their links as lines, here one hub with the things it calls. Line weight and labels show how much each link carries. Use it for an agent and its tools, a service and its dependencies or an account and its contacts.

Chartory ships it as a Figma component and a React component with the same name. The code installs from the shadcn registry with one command and lands in your project as a file you own.

What is the Network component?

It is one <Network> component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is a hub and its nodes, each with a value.

Sizes XS, S, M and L re-lay the chart out from the data instead of scaling it, so labels stay readable at every size.

When should I use it?

  • Is it one hub? Yes means the network fits.
  • Do links have no direction of flow? Yes means the network fits.
  • Is health not the point? Yes means the network fits.

When does another type fit better?

  • Flows between many groups. Use Chord instead.
  • Amounts flowing between steps. Use Sankey instead.
  • Healthy and failing links. Use Dependency map instead.

Network questions

Installing, data, Figma and plans.

  • Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.

Stay in the loop

New charts, by email.

Get an email when new chart types and releases ship.

Unsubscribe any time.