Brickroad
Brickroad
IndexSignalsBlog
/Index//

Product

  • Information Frontier Agent
  • Vendor Management Agent
  • Product Tour
  • Pricing

Solutions

  • All Solutions
  • Atlas
  • Wayfinder
  • Horizon

Suppliers

  • Sell Your Data
  • Start Onboarding
  • Programmatic Data License

Community

  • Public Index
  • Signals
  • Blog

Company

  • About
  • Team
  • Careers
  • Brand

Connect

  • LinkedIn
  • X
PrivacyTermsCookies

© 2026 Brickroad

/Index/Dome Systems/Governed AI-gateway telemetry
DS

Governed AI-gateway telemetry

DOME SYSTEMSManage supplier listing

Governed AI-gateway telemetry: a single normalised Audit v1 trail over every governed LLM/agent request, carrying allow / deny / filtered / failed outcomes, service and policy-path health, latency broken out per tool, model, gateway and rule evaluation, rate-limit and resource-exhausted quota events, and LLM consumption attributed by agent, API key, identity and served model across a six-class token partition (fresh input, cache-read, cache-write, output, hidden reasoning, call count) with per-class pricing applied at read time as estimated_cost_usd. Consumption is exposed as four read-time usage cubes plus time-series through documented REST endpoints (/api/v1/metrics/summary, /metrics/agents, /metrics/agents/{id}, /metrics/agents/{id}/keys), and usage history is explicitly retained after API-key revocation.

Open buyer room →
Dome Systems/Governed AI-gateway telemetry
SampleCoverage

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Dome Systems and files the sample in your catalog — private to you.

Start 7-day trial→Nothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry
Infrastructure Software
Instruments
equities
Categories
AlternativeFundamentalReference
Regions
US
Sample tickers
MSFTGOOGLNVDAAMDORCLSNOWDDOG
Dataset card
Type
not stated
Format
Tabular / structured JSON — normalised event records plus aggregation cubes, exposed as a REST metrics API and as OpenTelemetry traces, metrics and logs; event contracts are formally versioned (Audit v1, Event contracts reference)
Volume
Per workspace, 10^5-10^8 governed events and LLM calls per month is normal for an AI gateway sitting in front of agent traffic, each carrying the full token-class and outcome partition. Cross-tenant aggregate is therefore dominated by whichever few design partners are live; the dataset is deep per tenant but the tenant count is small.
Users
Very small: 6 employees on the company record with no funding stage on file, and the documentation is self-host-oriented (telemetry configured via environment variables on api-server/gateway), implying a design-partner-stage customer base — plausibly 5-30 enterprise workspaces rather than a broad installed base
History
2 years
Update frequency
not stated
Growth
Active, very early stage — a live, detailed and versioned documentation site (Audit v1 trail, event contracts reference, MCP tool alongside dashboard and CLI) indicates current heavy development; the company record shows 6 staff in West Menlo Park with no funding stage recorded
Launched
not stated
Delivery
not stated
Entity mapping
not stated
Sample
not stated
Point-in-time
not stated
Licence
not stated

supplier index read from their site

Dome Systems has not added their own details yet. Not yet on file:

  • Dataset
  • Data dictionary
  • Coverage
  • Provenance
  • Rights & data handling