Overview

Overview is the first item in the AgentHub sidebar and the page you land on when you open a project. It answers three questions for the project you have selected: how do I get started, how do I send traces, and what has this project done so far. The page header reads Overview, followed by “Get project name set up, then track models, evaluations, and spend as they happen.” The page has four sections, top to bottom:

1. Set up your first evaluation (two setup options)
2. Send your first trace (the integration guide)
3. Stat tiles: Models Configured, Evaluations Run, Total Cost Analyzed
4. Recent Runs

The first two sections render immediately. The stat tiles and the runs table load in the background and show a skeleton placeholder until their data arrives.

​

Set up your first evaluation

This card offers two ways to start, separated by an OR badge.

​

Option 1: Connect Your Model

For when you want to evaluate your own agent with your own provider key. The card lists the steps:

1. Open Model Manager from the sidebar
2. Add your provider + API key
3. Select a project and environment

The Go to Model Manager button opens Model Manager. If you already have a model configured, the link Jump straight to Cost Calculator. skips ahead to the Cost Calculator.

​

Option 2: Try a Project Template

“Fully configured agents with realistic mock data. One click to try.” Four featured templates are shown as cards. Each card shows the template name, a one-line description, and the connectors the agent uses. Clicking a card does not change your current project. It creates a new sibling project in the same organization, named after the template, with the template’s system prompt, tone, skills, memory and tools saved as a draft agent configuration. You are then taken to that new project’s Cost Calculator with the form already filled in. A toast confirms "<template name>" project created. While the request runs, the card reads Creating… and the other cards are blocked. The full template library (ten templates, including the Coding Agent Template) is available from the Start from… menu inside the Cost Calculator, which fills the current project’s form instead of creating a new project. See Cost Calculator templates.

​

Send your first trace

This section is the integration guide for teams that already run OpenTelemetry. AgentHub receives OTLP over HTTP, so you point your existing exporter at the endpoint and your spans appear under Traces. There is no proprietary SDK to install and no change to your call sites. The guide lists three steps:

1. Create a tracing key under Settings → Tracing Keys (links to Tracing keys)
2. Point your exporter at the endpoint and send the key as a bearer token
3. Run your agent. Spans arrive in Traces.

​

Connection details

Each row has a Copy button. After a successful copy it reads Copied. If the browser blocks clipboard access it reads Select to copy so you can select the text by hand. The endpoint is the base URL. Your exporter adds /v1/traces to it, so traces are posted to https://pillarforge.corepillar.ai/api/v1/traces.

​

Snippet tabs

The tabs give one runnable setup per language. Each tab has a short description and one or more code blocks, each with its own Copy button. The Env vars tab sets OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf. Several SDKs default to gRPC, which this endpoint does not accept.

​

Tracing key status

Below the tabs, a status line tells you whether the project already has a key: Only the newest non-revoked key is described. Both buttons open Settings → Tracing Keys. For the full ingestion contract, see the tracing quickstart.

​

Stat tiles

Three tiles summarize the selected project. They are always project-scoped, never org-wide.

​

How Total Cost Analyzed is calculated

1. AgentHub sums the recorded cost of every trace in the project, live traffic and Cost Calculator simulations alike, and counts those traces. A simulated scenario whose trace is missing is counted from its own result row instead, so no dollar is counted twice.
2. It divides cost by count to get a cost per request.
3. It multiplies that rate by a monthly request volume.

The default volume is the Cost Calculator’s default scale: 5,000 monthly users × 3 requests per user = 15,000 requests a month. If you have changed the scale for this project in the Cost Calculator’s Edit scale dialog, the tile uses your project’s figure instead. That setting is remembered in your browser, so a colleague on another machine sees the default until they set it too. The caption under the tile always says which basis it used, for example:

• “Projected at 5K users/mo — the platform default; this project has not set its own · from 42 recorded agent runs”
• “Projected at … — this project’s configured volume · from …”
• “Nothing recorded yet — run an evaluation to project spend” (when the project has no recorded cost yet; the tile shows $0.00)

Figures under $1 show cents. Larger figures are rounded to whole dollars.

​

Recent Runs

A table of the six most recent runs in the project, merged from two sources and sorted newest first:

• Cost Calculator runs, including drafts and runs that only generated scenarios
• Trace Evaluation runs (a collection applied to a single trace)

Clicking a Cost Calculator run opens it in the Cost Calculator (/cost-calculator?run=<id>), landing on its results when it has executed. Clicking a trace evaluation opens the trace it graded in Traces. Empty state: “No runs yet — Start your first evaluation above — connect a model or try a project template.”

​

Who can see this page

Any AgentHub user who is a member of the organization can open Overview. Users with the Viewer role are ModelHub-only and see “Your account has ModelHub access only” instead of AgentHub pages. See Roles and permissions.

​

Related