For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a product
    • Setting up a chat surface
    • Setting up an API surface
    • Setting up an MCP surface
    • Setting up an A2A surface
    • Setting up a Slack surface
    • Setting up a webhook surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to MCP clients
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and editing flows
    • Flow step types overview
    • Agent and flow templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
    • Braintrust (tracing)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Managing secrets
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate limits and usage
    • Managing Runtype with Claude
    • Agent skills
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • What you get
  • Connect Braintrust
  • What gets traced
  • Next steps
Integrations

Braintrust (tracing)

Was this page helpful?
Previous

What's in Settings?

Next
Built with

Connect your own Braintrust project to receive tracing spans for the executions you run through the Runtype API. This lets you observe your AI executions in your own Braintrust workspace alongside the rest of your LLM tooling.

What you get

Once connected, the executions you run through the Runtype API emit a runtype-execution trace span into your Braintrust project, tagged with execution metadata (user, organization, flow, and execution IDs). Use these spans to confirm which executions ran and correlate them with the rest of your LLM tooling.

This is an execution-level view: the runtype-execution parent span lands in your project, while model-level detail — individual prompt and completion spans, token usage, and latency — is captured in Runtype’s own platform observability. Connecting your project gives you a parallel execution-level copy in your workspace; it doesn’t replace or affect Runtype’s internal observability.

Connect Braintrust

  1. Sign up at braintrust.dev and create an API key.
  2. In Runtype, go to Settings → Integrations.
  3. Find Braintrust and enter your API key.
  4. Optionally set a project name — spans land in this Braintrust project. If you leave it blank, Runtype uses a project named Runtype.
  5. Click Save.

You can connect one Braintrust integration per organization. Your API key is encrypted at rest.

What gets traced

Tracing fires for every execution you run through the Runtype API — dispatch, product surfaces (chat, API, webhook, and A2A), agent runs, scheduled runs, batches, and evals. Spans are flushed in the background, so a Braintrust outage never slows down or blocks your execution.

Next steps

  • What are Logs? — inspect executions inside Runtype
  • What are Evals? — test and compare prompts and models
  • Connecting AI model providers — manage provider keys