Agco Ats AGCO Aftermarket Tools Service API

Name: AGCO Aftermarket Tools Service API
Brand: AGCO Aftermarket Tools Service API
Availability: InStock

✓ Official Vendor SpecIOTDevice Managementunauthenticated280 EndpointsREST

For Agents

Install Jentic One Beta

Connect the AGCO Aftermarket Tools Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AGCO Aftermarket Tools Service API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AGCO Aftermarket Tools Service API.

Look up engine production data and IQA codes by engine serial number

Retrieve ECU records by serial number for diagnostic workflows

Manage authorization codes and authorization categories that gate diagnostic tool features

GET STARTED

Start building with AGCO Aftermarket Tools Service API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AGCO Aftermarket Tools Service API for, with concrete tasks.

★ Dealer Diagnostic License Management

AGCO dealers issue, monitor, and revoke diagnostic tool licenses for their technicians via the ATS API. The LicenseActivations and AuthorizationCodes endpoints expose the per-technician entitlement so dealer admins can audit who can run which diagnostics on which equipment, replacing manual entitlement spreadsheets and offline sync jobs.

List active LicenseActivations for a specific dealer client and revoke any belonging to technicians no longer employed

Engine and ECU Lookup for Service

Service technicians look up an engine or ECU by serial number to retrieve production data, IQA codes, and aftermarket certificates before working on a tractor. The /AftermarketServices/Engines/{serialNumber}/* endpoints return the data in seconds, replacing paper service records and dealer-portal browsing during a workshop visit.

Given an engine serial number, fetch ProductionData and IQACodes and present a single service-history view to the technician

Localised Dealer Content Distribution

AGCO ships service content (procedures, fault codes, translations) to dealers via the ATS ContentSubmissions and TranslationSets endpoints. New procedures are submitted, translated for each market, and then assigned to the relevant UpdateGroups so dealer tools sync the latest content automatically. Replaces manual content packaging across regions.

List ContentSubmissions awaiting translation, push them through the TranslationSets endpoint for German and French, and assign the translated content to the EU UpdateGroup

AI Agent Service Operations

Through Jentic, an agent embedded in a dealer help desk can look up engine and ECU records, summarise authorization codes for a customer, and surface release-note context without holding the dealer's API credentials. The agent searches by intent, executes the right /api/v2 path, and returns the structured response.

Search Jentic for 'lookup tractor engine production data', load the schema for /api/v2/AftermarketServices/Engines/{serialNumber}/ProductionData, and execute it for a customer's serial number

Key Endpoints

280 endpoints — agco aftermarket tools service (ats) is the dealer-facing api for agco's agricultural equipment service ecosystem - tractors, engines, ecus, and aftermarket diagnostic tools across the massey ferguson, fendt, valtra, and challenger brands.

METHOD

PATH

DESCRIPTION

GET

/api/v2/AftermarketServices/Engines/{serialNumber}/ProductionData

Engine production data by serial number

GET

/api/v2/AftermarketServices/Engines/{serialNumber}/IQACodes

IQA codes for a specific engine

GET

/api/v2/AftermarketServices/ECUs/{serialNumber}

ECU record by serial number

GET

/api/v2/AftermarketServices/Certificates

Aftermarket certificate records

POST

/api/v2/Authentication

Authenticate a dealer user

GET

/api/v2/Clients

List dealer client accounts

GET

/api/v2/LicenseActivations

List diagnostic tool license activations

GET

/api/v2/Releases

List software releases

GET

/api/v2/AftermarketServices/Engines/{serialNumber}/ProductionData

Engine production data by serial number

GET

/api/v2/AftermarketServices/Engines/{serialNumber}/IQACodes

IQA codes for a specific engine

GET

/api/v2/AftermarketServices/ECUs/{serialNumber}

ECU record by serial number

GET

/api/v2/AftermarketServices/Certificates

Aftermarket certificate records

POST

/api/v2/Authentication

Authenticate a dealer user

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your AGCO dealer credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'look up tractor engine production data', and Jentic returns the matching ATS operation with its input schema so the agent picks the right v2 path without browsing the reference docs.

Time to first call

FAQs

Specific to using AGCO Aftermarket Tools Service API through Jentic.

What authentication does the AGCO ATS API use?

The OpenAPI spec does not declare a security scheme. In practice, the dealer-facing ATS API authenticates dealer users via POST /api/v2/Authentication and uses the resulting session for subsequent calls. Through Jentic, dealer credentials are stored encrypted and supplied at execution time.

Can I look up a tractor engine by serial number with this API?

Yes. GET /api/v2/AftermarketServices/Engines/{serialNumber}/ProductionData returns production data, and the sibling /IQACodes path returns the IQA code list. /api/v2/AftermarketServices/ECUs/{serialNumber} returns the ECU record.

What are the rate limits for the AGCO ATS API?

AGCO does not publish rate limits in the spec. The API is intended for dealer back-office and workshop tools rather than high-frequency public traffic - pace large reporting jobs and back off on HTTP 429.

How do I activate a diagnostic tool license through Jentic?

Search Jentic for 'agco activate diagnostic license', load the LicenseActivations schema, and execute the create call with the technician id and authorization code. Jentic returns the activation record confirming the technician now has access.

Which AGCO equipment brands does this API cover?

ATS supports the AGCO dealer network across Fendt, Massey Ferguson, Valtra, Challenger, and other AGCO brands. Lookups are by serial number rather than brand, but content and authorization codes are scoped per dealer client account.

Is this API for end customers or for dealers?

This API is for AGCO dealers, not end-customer telematics. End-customer fleet data lives in different AGCO products. Use ATS for dealer service operations - engines, ECUs, diagnostic licenses, content, and reporting.

Can I limit what my agent is allowed to do with the AGCO ATS API?

Yes. Because you run Jentic One yourself, your own rules decide which ATS operations and credentials the agent may use. Since AGCO puts the equipment serial number in the URL path for engine and ECU reads, such as GET /api/v2/AftermarketServices/Engines/{serialNumber}/ProductionData, you can pin the agent to reads for a single serial and grant only the operations you want, like reading production data or IQA codes. License activation, authorization codes, and dealer admin calls stay off limits unless you explicitly add them.