# How SiteTrax.io Data, Workflows and Agents Fit Together

Two flows answer different needs: SiteTrax.io can push processed data to a configured destination, and a connected assistant can request authorized information when a user asks a question. Enabling one flow does not configure the other.

## System architecture

[![Captured video becomes asset records through specialized detection and identifier reading. Records support configured delivery, authorized MCP queries and supported notifications. An assistant requests records and analytics; custom business workflows require separate tools and permissions.](https://docs.sitetrax.io/uploads/images/gallery/2026-10/scaled-1680-/07-intelligence-architecture.png)](https://docs.sitetrax.io/uploads/images/gallery/2026-10/07-intelligence-architecture.png)

[Open the architecture diagram at full size](https://docs.sitetrax.io/uploads/images/gallery/2026-10/07-intelligence-architecture.png). Solid arrows show documented paths; dashed boxes and arrows show separately scoped workflows. These are logical responsibilities, not a claim about physical hosting.

SiteTrax.io’s specialized models extract identifiers from captured imagery. A connected assistant’s foundation model interprets the user’s task, requests permitted SiteTrax.io results and explains the evidence. Broader actions require their own workflow, tools and permissions.

## Capture and create data

A compatible camera or capture app records equipment. The documented video-ingestion route uses configured object storage. Follow the storage-provider section for the supported service and upload requirements. SiteTrax.io processes the capture with its specialized detection and identifier-reading models, then stores operational results. The foundation model in your assistant is not required to perform this identifier extraction.

## Push data to an existing system

Configured project integrations can send output to a spreadsheet, a REST endpoint or an integration platform. This is a data-delivery route. Your receiving application decides how to use it. See [Organization Configuration](https://docs.sitetrax.io/books/administration/page/organization-configuration) and [API Output (JSON)](https://docs.sitetrax.io/books/sitetraxio-api/page/sitetraxio-api-output-json).

## Ask an assistant to retrieve and explain data

1. You ask a question in a connected assistant.
2. The assistant calls SiteTrax.io tools through the remote MCP endpoint.
3. SiteTrax.io applies the authenticated account’s project permissions and the requested filters.
4. SiteTrax.io retrieves records or calculates a supported aggregate.
5. The authorized result returns to the assistant provider for the response.

SiteTrax.io remains the source of the operational record. Query-time access sends the returned data to the chosen provider; it is not a promise that data stays entirely within a customer cloud. The deployed endpoint uses Streamable HTTP and OAuth. See [MCP Server](https://docs.sitetrax.io/books/mcp-server/page/sitetraxio-mcp-server).

## Run a workflow

Documented built-in notification workflows watch for new matching detections or send supported aggregate digests. A broader workflow that reads another system, evaluates a business rule and writes a result needs separate design and authorization. Choose the runtime, credentials, approval rules and support owner before deployment.

## Confirm responsibility before implementation

<table id="bkmrk-component-responsibi"><thead><tr><th>Component</th><th>Responsibility to establish</th></tr></thead><tbody><tr><td>Camera and site</td><td>Customer and SiteTrax.io agree coverage, installation and support responsibilities.</td></tr><tr><td>Raw capture storage</td><td>Confirm whether the bucket is customer-managed or SiteTrax-managed, plus access, retention and cost.</td></tr><tr><td>SiteTrax.io processing and records</td><td>SiteTrax.io supplies its processing service, records, supported analytics and access controls.</td></tr><tr><td>Assistant</td><td>Customer selects an approved provider and account. Provider policies govern its handling of returned results.</td></tr><tr><td>Custom workflow runtime</td><td>Name the cloud project owner, billing owner and support owner in the implementation scope.</td></tr><tr><td>External write actions</td><td>Name the destination, permitted actions, approval rule, audit record and failure recovery.</td></tr></tbody></table>

Data ownership, hosting location, access permissions and provider data handling are separate questions. A cloud provider’s certifications do not by themselves certify a SiteTrax.io deployment.