| Layer | What happens | What you receive |
|---|---|---|
| Capture | A compatible camera or capture app records equipment. | Video and available capture time and location. |
| SiteTrax.io data | Specialized processing reads supported identifiers and stores the results. | Records containing identifier text, type, status and project, with timestamps and evidence where available. |
| Intelligence | SiteTrax.io tools retrieve observations, calculate supported measures and run supported notifications. | An answer, analysis, detection alert or scheduled digest within the documented limits. |
| Connected assistant or agent | A validated assistant or agent client calls permitted tools and explains their results. | A response tied to the projects your account can access. Additional business actions need their own integration and permissions. |
| Everyday problem | What it costs | What Intelligence changes |
|---|---|---|
| Nobody can say where a unit is without walking the yard | Labour, delay, and a customer waiting on the phone | The last observation of an identifier is a lookup with its time, project and available image; it does not prove the unit is still there |
| Detention is billed and there is no way to check it | Charges paid that were never verified | Eligible gate-in and gate-out observations can support an inferred visit interval for invoice review; the applicable events, contract, free time, rate and exceptions still need verification |
| A dispute comes down to one party's recollection against another's | Write-offs and damaged relationships | Available timestamped observations and images help check the claimed movement |
| A KPI report takes a day to assemble | Reporting effort that crowds out operating | Totals and breakdowns are calculated on the server and returned on request |
| A camera stops producing and nobody notices for a week | A blind spot in the record exactly when it is needed | Recent camera activity and volume-gap checks identify a period to investigate; a gap alone does not prove hardware failure |
| Code | What it means |
|---|---|
| A0 | An accepted read under the processing rules; not independently verified accuracy. |
| I1 / I2 | A container owner-prefix warning / a failed container check-digit check. |
| I3 | No usable identifier was read. This does not prove physical damage. |
| I4 | A readable chassis or USDOT identifier was absent from the supplied asset list. The identifier is not necessarily invalid. |
| I5 | A synthetic missing container or chassis side of a combined pair, rather than a separately observed unit. |
| I6 | A low-confidence result that otherwise met the acceptance rules. |
| I7 | A configured text substitution changed the identifier after processing. Legacy display text may misleadingly describe it as low confidence. |
| - | Generic OCR has no semantic status classification; the dash is not automatically a warning. |
The profile belongs to a specific user account. If you publish a profile in the application but connect an assistant using a different SiteTrax.io account, that assistant will not see the profile. Use the same account on both sides.
# Core Intelligence Features  The application at [app.sitetrax.io](https://app.sitetrax.io) provides the profile interview, published revisions, coverage review and operational screens. A connected assistant uses the SiteTrax.io MCP server to query authorized data and perform the supported notification actions described below. ## Profile interview A short interview records who you are, the work you do, your goals, where you need visibility, other data you hold, operating costs and response preferences. Operating details can depend on the cost areas you select. Follow the questions shown for your account, and leave unknown figures unanswered rather than inventing a rate or baseline.  ## Published profile revisions Publishing creates an immutable revision. You can reopen and republish without replacing the history, and your published profile stays active while an edit is in progress. Only answers you explicitly confirmed are included; account-prefilled display values are not silently promoted into stored facts. ## Working brief A short summary of your published answers, stored with the revision and shown in the application. A connected assistant can retrieve a compact selection of published facts and priorities when relevant. The public MCP profile response excludes the working brief, custom AI instructions and response-style preferences. Publication does not guarantee that an assistant retrieves or applies your context. ## Coverage review The Intelligence hub shows guidance for supported visibility priorities from your interview, with a status on each card. Gate pairing is checked against the projects in your published scope. These cards help identify missing configuration or inputs; they do not certify that every movement was captured or that a contractual charge is due. ## Assistant connections The hub provides assistant setup entry points. A card opens setup but does not confirm installation or successful OAuth authorization. Complete [your provider’s dedicated setup section](https://docs.sitetrax.io/books/ai-integrations), then verify access by asking the assistant to list the projects your account can access. A published profile is optional for ordinary MCP queries. ## Operational data surfaces - **Dashboard** for volume, asset and scan totals over a period and project. - **Videos** for the recordings behind the readings, with the asset count found in each. - **Assets** for the gallery of readings, with an exceptions filter. - **Projects** for site configuration, user access and integrations. ## Record feedback Each asset record can be marked correct or incorrect from its detail page in the application. A connected assistant can read saved audit feedback for an exact record and retrieve its supporting observation. Submitting or changing record feedback remains an application action. ## Server-side analytics Counts, groupings, sequence analysis and anomaly checks are calculated by SiteTrax.io. Compare stored results or distinct recorded identifiers by project, camera, asset type, status and time. These are different measures: a result row or a distinct identifier is not automatically one physical unit or one gate passage. An assistant can request supported aggregates and then retrieve supporting records or inferred visits for explanation. Results are returned to the chosen assistant provider. Sequence analysis supports two to eight ordered observation stages for one equipment family at a time: containers, chassis or trailers. With defined boundaries and a suitable maximum visit duration, it can return completed-visit counts, average and median duration, percentiles such as p90, and time between stages. It also reports incomplete and ambiguous observations. Occupancy-versus-duration analysis describes an observed association under those assumptions; it does not establish the cause of a delay. Camera health summarizes recorded activity, status distributions and first/last observations. The review queue and anomaly checks help prioritize investigation; low activity does not prove an outage, and an A0 success-code share is not a measurement of OCR accuracy. ## Alerts and scheduled digests A connected assistant can create a watch for new matching detections, schedule an aggregate email digest, or cancel an existing alert or digest with your confirmation and the additional notification-write permission. Delivery is to your own verified account email. Listing notifications and reading delivery history require read permission only. See [Alerts and scheduled digests](https://docs.sitetrax.io/books/operational-use-cases/page/alerts-and-scheduled-digests) for supported conditions, schedules and limits. ## Reference and research Intelligence includes a curated library of SiteTrax.io product guidance and sourced logistics terminology. Reference material explains concepts; current records come from operational tools. Compatible research assistants can also search shared projects, matching equipment records, selected aggregate reports and reference entries, then retrieve the details behind a returned result. Assistant support for research and citations varies by platform. # Intelligence Roadmap Overview Use this page to distinguish documented Intelligence capabilities from a workflow that still needs implementation. Provider-specific availability belongs in each provider’s dedicated section. ## Documented capabilities - Operational record review and supported server-side analytics. - Authorized assistant access to shared projects. - Personal profile publication and native coverage guidance. - Defined detection alerts and supported aggregate email digests, with the required permission and confirmation. ## Requires a defined implementation A workflow that combines another business system with SiteTrax.io evidence, or performs downstream actions, needs an agreed scope. Confirm the trigger, data sources, runtime, permissions, approvals, support owner and acceptance criteria. The presence of an MCP connection does not establish an autonomous business workflow. ## Connection availability Use [the dedicated provider sections](https://docs.sitetrax.io/books/ai-integrations) for release status, setup and platform limits. A changed hub label does not by itself verify availability or authorization. Reviewed 7 October 2026 against published documentation. This page makes no release-date commitment. Contact SiteTrax.io for implementation scope and availability. # 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 [](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| Component | Responsibility to establish |
|---|---|
| Camera and site | Customer and SiteTrax.io agree coverage, installation and support responsibilities. |
| Raw capture storage | Confirm whether the bucket is customer-managed or SiteTrax-managed, plus access, retention and cost. |
| SiteTrax.io processing and records | SiteTrax.io supplies its processing service, records, supported analytics and access controls. |
| Assistant | Customer selects an approved provider and account. Provider policies govern its handling of returned results. |
| Custom workflow runtime | Name the cloud project owner, billing owner and support owner in the implementation scope. |
| External write actions | Name the destination, permitted actions, approval rule, audit record and failure recovery. |