Api Test Agrimetrics Agrimetrics Catalog API

Name: Agrimetrics Catalog API
Brand: Agrimetrics Catalog API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey, bearer93 EndpointsREST

For Agents

Discover Agrimetrics agri-environmental datasets, query their layers, run spatial queries with shapefiles, and download layer files via 93 catalogue endpoints.

Install Jentic One Beta

Connect the Agrimetrics Catalog API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agrimetrics Catalog 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 Agrimetrics Catalog API.

Authenticate against the Agrimetrics catalogue using either an APIM subscription key, a JWT, or one of the API-key schemes

Discover datasets and their associated layers via /datasets/{datasetId} and /datasets/{datasetId}/layers

Execute structured queries against the catalogue via /query for cross-dataset analysis

GET STARTED

Start building with Agrimetrics Catalog API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Agrimetrics Catalog API for, with concrete tasks.

★ Discover Datasets for an Agri Workflow

Walk the Agrimetrics catalogue programmatically to surface the datasets and layers that match an agri-environmental workflow, such as crop yield modelling or soil-type analysis. Calling /datasets/{datasetId} and /datasets/{datasetId}/layers gives the structural metadata needed to stitch together a downstream geospatial pipeline. The catalogue covers UK agri data published by Agrimetrics.

Call /datasets/{datasetId} for a candidate dataset, then /datasets/{datasetId}/layers to enumerate the layers and pick the ones that match the workflow

Spatial Query With a Custom Boundary

Upload a shapefile defining a farm boundary or a study region via /shapefile, then run /query against the Agrimetrics catalogue to retrieve only the layer values that fall within the boundary. This is the core pattern for scoped agri-environmental analysis: retrieve only the relevant pixels for a specific geographic area rather than downloading whole national layers.

POST a farm boundary shapefile to /shapefile, capture the returned id, and call /query with that boundary id and a chosen layer id

Layer File Download Pipeline

Pull layer file contents via /layers/{layerId}/files into a downstream raster or vector pipeline. The endpoint returns the underlying file references for a chosen layer, which a processing job can then download and feed into GIS tooling. This is useful when the workflow needs the raw layer data rather than catalogue metadata.

Call /layers/{layerId}/files for a chosen layer id, capture the file references, and queue them for download into the GIS pipeline

Agent Integration via Jentic

An AI agent built on Jentic can search for the Agrimetrics catalogue operations by intent and execute them without holding the APIM subscription key in agent context. Jentic's MAXsystem holds the credential and returns scoped access at call time, which matters when an agri-tech workflow combines Agrimetrics with multiple other geospatial providers.

Use Jentic search for 'list agrimetrics datasets', load the dataset endpoint, execute it, and pass the chosen dataset id into a follow-up layers call

Key Endpoints

93 endpoints — agrimetrics catalog api exposes the agri-environmental data catalogue published by agrimetrics, covering datasets, layers, query execution, and shapefile uploads for spatial analysis.

METHOD

PATH

DESCRIPTION

POST

/authenticate

Authenticate against the catalogue

GET

/status

Catalogue status check

POST

/query

Run a structured catalogue query

GET

/datasets/{datasetId}

Read a dataset by id

GET

/datasets/{datasetId}/layers

List the layers belonging to a dataset

POST

/shapefile

Upload a shapefile to scope subsequent queries

GET

/layers/{layerId}

Read layer metadata by id

GET

/layers/{layerId}/files

Get the file references for a layer

POST

/authenticate

Authenticate against the catalogue

GET

/status

Catalogue status check

POST

/query

Run a structured catalogue query

GET

/datasets/{datasetId}

Read a dataset by id

GET

/datasets/{datasetId}/layers

List the layers belonging to a dataset

Why Jentic?

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

Credential isolation

Whichever Agrimetrics auth scheme you use (APIM subscription key, JWT, x-user header, or API key) is stored encrypted in the Jentic vault. Agents receive scoped execution tokens at call time and never hold the raw credential.

Intent-based discovery

Agents search by intent such as 'list agrimetrics datasets' or 'run a shapefile spatial query' and Jentic returns the matching operation across the 93 endpoints with its full input schema, so the agent can call the right endpoint without reading the docs.

Time to first call

Direct integration: 2-3 days to wire one of the auth schemes, dataset discovery, and shapefile-scoped queries. Through Jentic: under 2 hours from search to first executed call.

FAQs

Specific to using Agrimetrics Catalog API through Jentic.

What authentication does the Agrimetrics Catalog API use?

Multiple schemes are supported: an Azure APIM subscription key in ocp-apim-subscription-key, a JWT bearer token, an apiKeyHeader or apiKeyQuery API key, and an x-user header. Use whichever matches your Agrimetrics account setup. Through Jentic the credential is held in the vault and only a scoped token is granted to the agent at call time.

Can I run spatial queries scoped to a custom boundary?

Yes. POST a shapefile to /shapefile to register a boundary, then call /query referencing that boundary id and the chosen layer id. The catalogue returns only the layer values that fall within the supplied geometry.

What are the rate limits for the Agrimetrics Catalog API?

The OpenAPI spec does not declare explicit rate limits. Treat the API as standard HTTPS and respect any 429 responses; check your Agrimetrics account dashboard for the contractual ceiling for your subscription tier.

How do I list available datasets through Jentic?

Install the Jentic SDK with pip install jentic, search for 'list agrimetrics datasets', load the dataset operation, and execute it. Sign up at https://app.jentic.com/sign-up to get a Jentic agent key.

Is api-test.agrimetrics.co.uk the production host?

No. api-test.agrimetrics.co.uk is the test host published in this spec. For production traffic you may need to repoint to the live Agrimetrics host once your Agrimetrics representative provides credentials, while keeping the same endpoint shapes.

Can I download the underlying layer files?

Yes. GET /layers/{layerId}/files returns the file references for a chosen layer, which a downstream pipeline can then fetch into GIS tooling. Pair with /datasets/{datasetId}/layers to discover which layer ids belong to a dataset.

Api Test Agrimetrics Agrimetrics Catalog API

Connect the Agrimetrics Catalog API to your agent

Capabilities

Start building with Agrimetrics Catalog API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs