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 8 API contracts indexed on the APIs.io network, including Fields API, Boundaries API, Exports API, and 5 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 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

45.7/100 developing ▬ flat Agent 30/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract

AgricultureBayerCrop DataField Boundaries Harvest OAuthPlantingPrecision Agriculture AgTech Authentication

What this lets a business do 4

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Crop Production Management

BC-3500

ApplicationPlanting

Agronomy & Farm Advisory Management

BC-3530

Soil Sampling

Farm Land & Asset Management

BC-3540

Fields

GET /v4/fields GET /v4/fields/{fieldId}

Harvest & Post-Harvest Operations Management

BC-3560

Harvest

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 45.7/100 · developing

Contract Quality 11.3 / 19

Developer Ergonomics 8.0 / 15

Access Clarity 4.3 / 15

Operational Transparency 2.8 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 5.1 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 30/100 · agent ready

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

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/climate-fieldview/"><img src="https://apis.io/badge/climate-fieldview/card.svg" alt="Climate FieldView on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 28.9 — up to +14.2 composite points
Contract Governance scores 13.6 — up to +10.4 composite points
Contract Quality scores 60.1 — up to +10.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/climate-fieldview/apis.yml: open an issue on github.com/api-evangelist/climate-fieldview to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Agriculture and Food (Farm Data, Nutrition)	gravity	51.8	-	-
APIs.guru OpenAPI Directory (API definition directory)	gravity	51.8	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OAuth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 8

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

Climate FieldView Fields API

Agricultural field boundaries and metadata

Climate FieldView Boundaries API

Field Boundary data endpoints.

Climate FieldView Exports API

General data export endpoints.

Climate FieldView Farm Organizations API

Farm organization data endpoints.

Climate FieldView Layers API

General data retrieval endpoints.

Climate FieldView Operations API

Operation data endpoints.

Climate FieldView Resource Owners API

Resource Owner data endpoints.

Climate FieldView Uploads API

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Climate FieldView's documentation. All 5 limits →

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

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Climate FieldView

SLA

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 — jsonschema 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

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Plans

FinOps

TermsOfService

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
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  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
- OAuth
- Planting
- Precision Agriculture
- AgTech
- Authentication
tags_raw:
- Agriculture
- Bayer
- Crop Data
- Field Boundaries
- Harvest
- OAuth2
- Planting
- Precision Ag
- AgTech
- Authentication
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-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-boundaries-api
  name: Climate FieldView Boundaries API
  description: Field Boundary data endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Boundaries
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-boundaries-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-exports-api
  name: Climate FieldView Exports API
  description: General data export endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Export
  tags_raw:
  - Exports
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-exports-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-farmorganizations-api
  name: Climate FieldView Farm Organizations API
  description: Farm organization data endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - FarmOrganizations
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-farmorganizations-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-layers-api
  name: Climate FieldView Layers API
  description: General data retrieval endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Layers
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-layers-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-operations-api
  name: Climate FieldView Operations API
  description: Operation data endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags: []
  tags_raw:
  - Operations
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-operations-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-resourceowners-api
  name: Climate FieldView Resource Owners API
  description: Resource Owner data endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - ResourceOwners
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-resourceowners-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-uploads-api
  name: Climate FieldView Uploads API
  description: General data upload endpoints.
  humanURL: https://dev.fieldview.com/
  baseURL: https://api.climate.com
  tags:
  - Uploads
  properties:
  - type: OpenAPI
    url: openapi/climate-fieldview-uploads-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: Plans
  url: plans/climate-fieldview-plans-pricing.yml
- type: RateLimits
  url: rate-limits/climate-fieldview-rate-limits.yml
- type: FinOps
  url: finops/climate-fieldview-finops.yml
- 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

Climate FieldView API — frequently asked questions

Does Climate FieldView have an API?

Yes. APIs.io lists 8 APIs from Climate FieldView, including Climate FieldView Fields API, Climate FieldView Boundaries API and Climate FieldView Exports API, and 5 more.

Is there an OpenAPI specification for the Climate FieldView API?

Yes. APIs.io indexes 8 OpenAPI specifications for Climate FieldView, each linked for download from this page.

How do I authenticate with the Climate FieldView API?

Climate FieldView documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Climate Fieldview Authentication.

How much does the Climate FieldView API cost?

APIs.io lists 3 pricing plans for Climate FieldView, with each plan's price, limits and inclusions under Pricing on this page.

Is the Climate FieldView API ready for AI agents?

Climate FieldView has a Kin Score of 45.7 out of 100 (developing) and an Agent Readiness score of 29.6 (agent-ready), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.