How Intelligence Uses SiteTrax.io Data

Intelligence does not hold its own copy of your operation. It reads the records SiteTrax.io already stores, applies your published profile as context, and returns results scoped to the projects your account is permitted to see.

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 reads the identifiers in that video and stores each reading as an asset record with a status code.
3. The record. Each record carries the identifier text, the asset type, the project, the scan and processing times, direction of travel, camera, coordinates where available, a confidence value, and a link to the image.
4. Intelligence. Your published profile supplies the operating context. Aggregations, sequences and exception checks are calculated on the server.
5. Delivery. The result is shown in the application, or returned to a connected assistant through the MCP server.

How to read an asset record

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. Entering and exiting reflect how the site and its cameras are set up.

Your profile as context

When you publish the profile interview, SiteTrax.io stores an immutable revision and generates a short working brief from your answers. That brief is what an assistant receives as context: your role, your priorities, the costs you flagged, the sources you already have, and the response style you asked for.

Custom AI instructions are stored alongside the revision rather than merged into the brief. Your answers are customer-supplied context, not independently verified operational evidence, and SiteTrax.io treats them that way.

Scope and permissions

Every request is limited to the projects shared with the authenticated account. Connecting an assistant does not widen SiteTrax.io permissions. If a project has not been shared with you, it is not in scope for the application or for an assistant acting on your behalf.

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.