Glossary
Glossary of agrirouter terms and abbreviations
Definitions for the terms and abbreviations used throughout the agrirouter documentation.
| Term | Definition |
|---|---|
| agrirouter | Universal data exchange platform for agriculture, connecting machines, software, and services across manufacturer boundaries. |
| App / Application | A software product registered with agrirouter. Each application receives a unique application ID and is managed through the agrirouter developer portal. |
| App Provider | The company that builds and operates an application integrated with agrirouter. Holds a developer account and is responsible for the integration's technical side (authorization, endpoint creation, messaging). See App Providers. Previously sometimes called "solution provider". |
| CAP / Capabilities | Declaration of which technical message types an endpoint can send and/or receive. Capabilities are included in the endpoint creation request and updated whenever they change. |
| Cloud Software | A cloud-hosted application that integrates with agrirouter on behalf of an end user. Registered as the cloud_software endpoint type. Replaces the legacy "Farming Software" and "Telemetry Platform" framings. |
| CU / Communication Unit | A physical hardware device (terminal, telemetry box, or ISOBUS gateway) that connected to agrirouter via the legacy API. Not an endpoint type in the current API: new hardware integrations register as a virtual_communication_unit instead. See Migrating from Legacy. |
| DDI / Data Dictionary Identifier | Standardized numeric identifiers for sensor values and task parameters, defined by the ISOBUS standard (ISO 11783). |
| DVC / Device Description | An EFDI message that describes the devices (implements, sensors) attached to a Communication Unit or VCU. |
| EFDI | Extended Farm Device Interface, a protobuf-based format used by agrirouter for transmitting device descriptions and live telemetry data. |
| EP / Endpoint | The representation of a software or hardware instance within the agrirouter platform. Each application instance connected to agrirouter becomes an endpoint. |
| Farming Software | Legacy framing for a cloud or desktop application that exchanges agricultural data with agrirouter. Deprecated as an endpoint type: new applications should register as cloud_software. The farming_software value is still accepted for backward compatibility. See Migrating from Legacy. |
| Feed | Temporary storage within agrirouter for unread messages destined for a specific endpoint. Messages remain in the feed until retrieved or expired. |
| ISOBUS | ISO 11783, the international standard for serial data communication between agricultural electronics, including tractors, implements, and farm software. |
| ISOXML | An XML-based data format for task data defined by ISO 11783-10. Used for exchanging prescriptions, field boundaries, and recorded task results. |
| IT / Information Type | A user-facing grouping of related technical message types. Information types simplify routing configuration for end users by bundling similar data formats together. |
| MSG / Message | A unit of data exchanged between endpoints through the agrirouter platform. Each message has a header (metadata) and a body (payload). |
| MQTT | Message Queuing Telemetry Transport, a lightweight publish/subscribe protocol used as the legacy transport layer for agrirouter communication. |
| REST | Representational State Transfer, an HTTP-based protocol style used as a transport layer for agrirouter communication. |
| Route | A connection configured by the account owner in the agrirouter UI that allows messages of a given information type to flow between two endpoints. Previously called "routing rule" in older documentation, and sometimes called "routing" in the UI. See Migrating from Legacy. |
| SSE | Server-Sent Events, a unidirectional protocol used by the current API for receiving real-time events from agrirouter. |
| TeamSet | A collection of devices reported by a Communication Unit or VCU. Each TeamSet has a unique TeamSet ID and represents the current configuration of attached implements. See TeamSet Context ID. |
| TeamSet Context ID | The identifier for a TeamSet passed on the wire as the x-agrirouter-teamset-context-id header. Sometimes also called "TeamSet ID". See TeamSet Context ID. |
| Telemetry Platform | Legacy framing for a cloud application that acted as a concentrator for a fleet of machines. The current API has no telemetry_platform endpoint type: a cloud application is registered as cloud_software, and each machine is registered directly as its own virtual_communication_unit endpoint. See Migrating from Legacy. |
| TMT / Technical Message Type | A specific data format identifier used by agrirouter to classify messages (e.g., iso:11783:-10:taskdata:zip). Capabilities and routes are defined in terms of TMTs. |
| TP | Legacy abbreviation for Telemetry Platform. See Telemetry Platform. |
| VCU / Virtual Communication Unit | An endpoint that represents a physical machine (tractor, implement, or ISOBUS-connected unit) participating in data exchange. Registered as the virtual_communication_unit endpoint type via its own PUT /endpoints/{externalId} call, with its own external ID, capabilities, subscriptions, and feed. |
| URN | Uniform Resource Name, a standardized naming format used for external identifiers in agrirouter, such as endpoint IDs. |