Climate FieldView

Climate FieldView is a digital agriculture platform from Bayer (originally developed by The Climate Corporation) that gives growers, agronomists, and agribusiness partners a single view of field-level operations. The platform ingests as-planted, as-applied, and as-harvested data from field equipment, combines it with imagery, weather, and soil layers, and exposes those agronomic datasets through a REST API at api.climate.com. Authentication is via OAuth 2.0 authorization-code grant, and resources include fields, planting and harvest activities, application records, and soil samples.

Climate FieldView publishes 5 APIs on the APIs.io network, including Application API, Fields API, Harvest API, and 2 more. Tagged areas include Agriculture, Bayer, Crop Data, Field Boundaries, and Harvest.

The Climate FieldView catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

Climate FieldView’s developer surface includes authentication, developer portal, documentation, getting-started guide, engineering blog, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub

44.8/100 developing ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessFreemiumSelf serve⚡ Free to try

1 APIs

AgricultureBayerCrop DataField BoundariesHarvest Authentication PlantingPrecision Ag

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 44.8/100 · developing

Contract Quality 13.7 / 23

Developer Ergonomics 9.6 / 18

Access Clarity 6.6 / 18

Operational Transparency 3.4 / 12

Contract Governance 1.5 / 11

Discoverability 6.2 / 9

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/climate-fieldview: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Climate FieldView Application API

As-applied agrochemical data

Climate FieldView Fields API

Agricultural field boundaries and metadata

Climate FieldView Harvest API

As-harvested yield data and maps

Climate FieldView Planting API

As-planted activity data and maps

Climate FieldView Soil Sampling API

Soil sample results and layers

Postman Collections 5

Ready-to-run Postman collections for exercising this provider's APIs.

Climate FieldView Platform Application API

POSTMAN

Climate FieldView Platform Application Fields API

POSTMAN

Climate FieldView Platform Application Harvest API

POSTMAN

Climate FieldView Platform Application Planting API

POSTMAN

Climate FieldView Platform Application Soil Sampling API

POSTMAN

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Climate FieldView Platform Application API

OPEN COLLECTION

Climate FieldView Platform Application Fields API

OPEN COLLECTION

Climate FieldView Platform Application Harvest API

OPEN COLLECTION

Climate FieldView Platform Application Planting API

OPEN COLLECTION

Climate FieldView Platform API

OPEN COLLECTION

Climate FieldView Platform Application Soil Sampling API

OPEN COLLECTION

Scroll for all 7

Pricing Plans 1

Published pricing tiers and plan structures.

Climate Fieldview Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Climate Fieldview Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Climate Fieldview Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Climate Fieldview Context

2 classes · 23 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Climate FieldView API Rules

6 rules · 4 warnings 2 info

SPECTRAL

Climate FieldView API Rules

6 rules · 4 errors 2 warnings

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

Climate FieldView Field

11 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Climate Fieldview Authentication

oauth2 · 1 scheme

SECURITY

Climate Fieldview Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Climate Fieldview Scopes

5 scopes · authorizationCode

5 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Climate Fieldview Agentic Access

11 operations · 1 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Portal

Portal

GettingStarted

GettingStarted

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

OpenAPI

OpenAPI

JSONSchema

JSONSchema

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

JSONLDContext

JSONLDContext

Spectral

Spectral

Build 2

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

GitHubOrg

GitHubOrg

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Authentication

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

LinkedIn

Website

Website

Partners

Partners

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: climate-fieldview
name: Climate FieldView
url: https://raw.githubusercontent.com/api-evangelist/climate-fieldview/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
created: '2025-03-05'
modified: '2026-05-19'
specificationVersion: '0.23'
type: Index
access: 3rd-Party
position: Consuming
kind: company
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/climate-fieldview.png
tags:
- Agriculture
- Bayer
- Crop Data
- Field Boundaries
- Harvest
- Authentication
- Planting
- Precision Ag
tags_raw:
- Agriculture
- Bayer
- Crop Data
- Field Boundaries
- Harvest
- OAuth2
- Planting
- Precision Ag
description: Climate FieldView is a digital agriculture platform from Bayer (originally developed by The Climate Corporation)
  that gives growers, agronomists, and agribusiness partners a single view of field-level operations. The platform ingests
  as-planted, as-applied, and as-harvested data from field equipment, combines it with imagery, weather, and soil layers,
  and exposes those agronomic datasets through a REST API at api.climate.com. Authentication is via OAuth 2.0 authorization-code
  grant, and resources include fields, planting and harvest activities, application records, and soil samples.
apis:
- aid: climate-fieldview:climate-fieldview-application-api
  name: Climate FieldView Application API
  description: As-applied agrochemical data
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Application
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-application-api-openapi.yml
  - type: Documentation
    url: https://dev.fieldview.com/technical-documentation/
  - type: Authentication
    url: https://dev.fieldview.com/api-details/
  - type: FAQ
    url: https://dev.fieldview.com/faq/
  - type: ChangeLog
    url: https://dev.fieldview.com/technical-documentation/next-versions/
  - type: SDKs
    url: https://github.com/TheClimateCorporation/api-example
- aid: climate-fieldview:climate-fieldview-fields-api
  name: Climate FieldView Fields API
  description: Agricultural field boundaries and metadata
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Fields
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-fields-api-openapi.yml
  - type: Documentation
    url: https://dev.fieldview.com/technical-documentation/
  - type: Authentication
    url: https://dev.fieldview.com/api-details/
  - type: FAQ
    url: https://dev.fieldview.com/faq/
  - type: ChangeLog
    url: https://dev.fieldview.com/technical-documentation/next-versions/
  - type: SDKs
    url: https://github.com/TheClimateCorporation/api-example
- aid: climate-fieldview:climate-fieldview-harvest-api
  name: Climate FieldView Harvest API
  description: As-harvested yield data and maps
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Harvest
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-harvest-api-openapi.yml
  - type: Documentation
    url: https://dev.fieldview.com/technical-documentation/
  - type: Authentication
    url: https://dev.fieldview.com/api-details/
  - type: FAQ
    url: https://dev.fieldview.com/faq/
  - type: ChangeLog
    url: https://dev.fieldview.com/technical-documentation/next-versions/
  - type: SDKs
    url: https://github.com/TheClimateCorporation/api-example
- aid: climate-fieldview:climate-fieldview-planting-api
  name: Climate FieldView Planting API
  description: As-planted activity data and maps
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Planting
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-planting-api-openapi.yml
  - type: Documentation
    url: https://dev.fieldview.com/technical-documentation/
  - type: Authentication
    url: https://dev.fieldview.com/api-details/
  - type: FAQ
    url: https://dev.fieldview.com/faq/
  - type: ChangeLog
    url: https://dev.fieldview.com/technical-documentation/next-versions/
  - type: SDKs
    url: https://github.com/TheClimateCorporation/api-example
- aid: climate-fieldview:climate-fieldview-soil-sampling-api
  name: Climate FieldView Soil Sampling API
  description: Soil sample results and layers
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Soil Sampling
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-soil-sampling-api-openapi.yml
  - type: Documentation
    url: https://dev.fieldview.com/technical-documentation/
  - type: Authentication
    url: https://dev.fieldview.com/api-details/
  - type: FAQ
    url: https://dev.fieldview.com/faq/
  - type: ChangeLog
    url: https://dev.fieldview.com/technical-documentation/next-versions/
  - type: SDKs
    url: https://github.com/TheClimateCorporation/api-example
common:
- type: CapabilityMap
  url: capabilities/climate-fieldview-capability-edges.yml
  name: Climate FieldView Business Capability Map
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/climate-fieldview/overview
- type: AgenticAccess
  url: agentic-access/climate-fieldview-agentic-access.yml
- type: DomainSecurity
  url: security/climate-fieldview-domain-security.yml
- type: Authentication
  url: authentication/climate-fieldview-authentication.yml
- type: OAuthScopes
  url: scopes/climate-fieldview-scopes.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/climate-llc
- type: Website
  url: https://climate.com/
- type: Portal
  url: https://dev.fieldview.com/
- type: Documentation
  url: https://dev.fieldview.com/technical-documentation/
- type: Authentication
  url: https://dev.fieldview.com/api-details/
- type: GettingStarted
  url: https://dev.fieldview.com/faq/
- type: TermsOfService
  url: https://climate.com/en-us/legal/terms-of-service.html
- type: PrivacyPolicy
  url: https://climate.com/legal/privacy-policy
- type: GitHubOrg
  url: https://github.com/TheClimateCorporation/api-example
- type: Partners
  url: https://climate.com/partners
- type: OpenAPI
  url: openapi/_original/climate-fieldview-platform-openapi.yml
- type: JSONSchema
  url: json-schema/climate-fieldview-field-schema.json
- type: JSONLDContext
  url: json-ld/climate-fieldview-context.jsonld
- type: Spectral
  url: rules/climate-fieldview-rules.yml
- url: https://climate.com/en-us/resources/blog.html
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/climate-fieldview"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/climate-fieldview/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/climate-fieldview/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.