Introduction to SiteTrax.io Intelligence

• What is SiteTrax.io Intelligence?
• Why Intelligence Matters
• How Intelligence Uses SiteTrax.io Data
• Core Intelligence Features
• Intelligence Roadmap Overview

What is SiteTrax.io Intelligence?

SiteTrax.io Intelligence is the layer of SiteTrax.io that turns captured yard and gate activity into answers you can act on. It is available within the application at app.sitetrax.io and through authorized assistant connections to the SiteTrax.io MCP server.

What it does

SiteTrax.io cameras and capture apps provide records of activity at gates, yards, ramps and docks. Processing stores result rows for supported equipment such as containers, chassis, trailers and trucks, with available timestamps, project, status, heading and media links. A result row is not always a successful identifier read or an independent observation of a physical unit.

Intelligence sits on top of that record and helps in four ways.

• It holds a profile of your operation. A profile interview captures your work, goals, visibility needs, costs and response preferences. Confirmed answers are published as a profile revision. A connected assistant can retrieve selected facts and priorities when relevant; the public profile response excludes the saved working brief, custom instructions and response-style preferences.
• It reviews your coverage. The native hub uses the areas you selected and available project configuration to identify useful next steps. It distinguishes confirmed inputs from coverage that still needs your confirmation. These informational cards do not prove complete capture or activate a persistent monitoring workflow.
• It provides assistant access. After you authorize a supported assistant through OAuth, that assistant can query the SiteTrax.io data your account is allowed to read. The hub provides setup links; operational conversation and tool use take place in the assistant.
• It answers operational questions. Server-side tools support equipment history, activity totals, status and type breakdowns, inferred movement sequences, camera activity checks and anomaly review. Supported alerts and scheduled digests can be created after you confirm the change and grant notification-write permission.

Where to find it

Sign in at app.sitetrax.io and select Intelligence in the left navigation.

When Intelligence is enabled, its navigation item appears after you publish a profile for your account. Until then, the interview is the native setup entry point. See Accessing SiteTrax.io Intelligence. You can also connect an assistant directly without publishing a profile; ordinary MCP access requires an active, email-verified account and separate authorization.

What it is not

• It is not a second copy of your data. Intelligence queries the same SiteTrax.io records the rest of the application uses. MCP access does not require a separate bulk synchronized warehouse, but requested results are sent to the assistant provider you authorize.
• It does not replace the SiteTrax.io record. SiteTrax.io remains the system of record. Operational results can be checked against their supporting observations, times and projects. Image availability depends on project permissions, retention and redaction; profile answers are customer-supplied context.
• It is not a forecasting engine. Intelligence reports what was observed and the intervals between observations. It does not assert why an interval happened.

Documentation that referred to service.sitetrax.io describes the retired portal. The current application is app.sitetrax.io.

Why Intelligence Matters

Captured yard and gate records are more useful when operators can find and compare them while a decision is still in front of them. Intelligence makes those records easier to query and shows where missing capture limits the answer.

The problems it addresses

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

Why trusted data is the point

An assistant can ground an answer in the SiteTrax.io records your account is allowed to read. Times, projects, result types, status codes and available images make those records reviewable. Some processing rows are synthetic or contain unsuccessful reads, and media can be missing or redacted, so evidence should be checked before using it in a dispute or invoice review.

Supported analytics report relevant limits, such as incomplete pairings, capped result lists or an unavailable calculation. Inferred visits remain estimates derived from eligible observations and stated pairing rules. Ask the assistant to explain missing data and uncertainty rather than treating an observation gap as a confirmed movement.

Who gets value from it

• Gate staff review captured arrivals and departures using the site's direction configuration.
• Yard supervisors review recent observations and inferred visits, with capture and pairing limits stated.
• Customer service finds the last recorded location and time without leaving their desk.
• Operations managers compare volume and dwell across sites and periods.
• Finance and executives get counts they can defend, drawn from the same records the yard works from.

How Intelligence Uses SiteTrax.io Data

Intelligence reads the records SiteTrax.io already stores and returns operational results scoped to the projects your account is permitted to see. The native hub uses your published profile for personal guidance. A connected assistant can retrieve selected published facts and priorities when relevant to a request.

The chain from camera to answer

1. Capture. A camera or capture app records video at a gate, in a yard, or on a route.
2. Processing. SiteTrax.io processes the capture and stores asset/result rows with identifier text, emitted type and status code. Some rows represent failed reads or a synthetic missing side of a container/chassis pair, rather than an independently identified unit.
3. The record. A record contains stored identifier text, type, project and processing status, with scan time, camera, heading, coordinates, confidence and media links where available. Direction requires the relevant heading or site designation, and retention or redaction can withhold media.
4. Intelligence. Aggregations, sequences and exception checks are calculated on the server. An assistant can request published profile context separately when it helps answer your question.
5. Delivery. The result is shown in the application, or returned through the MCP server to the assistant provider you connected. Query-time access avoids a separate bulk synchronized index; it still sends the requested results to that provider.

How to read an asset record

For a full equipment history, confirm both the complete identifier and the equipment type. Text search can find partial matches, and the same text can occur in different equipment families.

Reading these records correctly matters more than any single feature, because a misread record produces a confident wrong answer.

• One record is one stored processing result. It is not guaranteed to be one physical asset or one direct observation. Where container and chassis processing are combined, SiteTrax.io can add a synthetic row for the paired side.
• Identifier text is only usable when it is real text. Blank values and placeholders such as a single dash are not equipment identifiers and must not be treated as one.
• Status code and asset type must be read together. A processing status describes the outcome of reading the image. It is not by itself a statement about the physical condition of the unit.
• Counts mean what they say. A count of records is not the same as a count of distinct units, and a count of distinct identifier values is not a guarantee of distinct equipment.
• Direction is configuration-dependent. It can describe movement derived from a record's heading and stored direction mapping, or the designated role of a project or camera. Ask which interpretation was used. Vertical or missing headings do not establish heading-derived entry or exit.

Common status interpretations

Read status and emitted asset type together. These examples describe processing outcomes and do not independently establish an operational incident.

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 share of rows carrying A0 is a processing-result measure. It should not be labeled OCR accuracy without a defined eligible population and independently verified outcomes.

Dates and evidence

Asset analysis uses scan time when present and falls back to record creation time for older records. Video analysis uses video creation time. Ordinary MCP date filters use UTC-midnight business-day boundaries; a grouping timezone changes the displayed time buckets. Sequence analysis can instead use exact timezone-aware start and end timestamps for local calendar periods. State the requested timezone and check the resolved boundaries in the answer.

Your profile as context

When you publish the profile interview, SiteTrax.io stores an immutable revision and generates a working brief for review in the application. The public MCP profile tool returns selected facts and priorities from your latest published revision. Available sections include organization, operations, inferred user timezone, confirmed tailored answers and the accessible projects from the publication snapshot. It does not return the working brief, custom AI instructions or response-style preferences.

Custom AI instructions and response preferences can be saved in your profile, but saving them does not configure a connected assistant. Ask for the desired tone or level of explanation in that assistant. Profile retrieval and use depend on the assistant and the question. Your published answers remain customer-supplied context, not independently verified operational or contractual evidence. A saved free-time allowance or rate alone does not establish a payable charge.

Publishing also snapshots the projects covered by that revision. Profile retrieval keeps only snapshotted projects you can still access; newly shared projects are not automatically added to the old publication. Reopen and republish when the intended profile scope changes. If no projects remain accessible, or the returned profile list is incomplete, the assistant must make that limitation clear rather than silently querying all shared projects.

Scope and permissions

For an operational question, explicitly name the projects you want analyzed. A profile provides context, while each data request has its own project selection. Omitted project filters normally mean all projects currently shared with the authenticated account.

Every operational request is limited to the projects currently shared with the authenticated account. Connecting an assistant does not widen SiteTrax.io permissions. Projects selected in a profile describe context; they are not a separate OAuth project grant. Current project sharing remains the access limit. See Account access and OAuth.

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 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 setup entry points for ChatGPT and Claude. Complete the connection in the assistant using an active, email-verified SiteTrax.io account and approve its OAuth access. The hub cards do not confirm installation or successful authorization. A published profile is optional for ordinary authorized MCP queries. See Account access and OAuth.

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 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

Status reviewed: 22 September 2026. This page records the availability shown in the application and separates setup links from completed assistant authorization. It does not promise a release date.

In build

Item	Status shown in the application	What to do today
Microsoft Copilot connection	Listed on the Intelligence hub as coming soon. The application states the SiteTrax.io connection for Copilot is still being built.	Use ChatGPT or Claude for assistant access in the meantime. See Supported AI Platforms.

Available now

The profile interview, published revisions, coverage guidance, and setup entry points for ChatGPT and Claude are available in the application. Each assistant connection still requires its own supported account or workspace and successful OAuth authorization. They are documented in Getting Started and AI Integrations.

How this page is maintained

This page should be updated when a product announcement or verified availability changes. If you need a commitment on timing for a specific capability, contact SiteTrax.io.

If the application and this page show different availability, consult Supported AI Platforms and report the discrepancy. A changed hub label alone does not confirm public availability or access in your assistant workspace.