Platform Climate FieldView Platform API
★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controloauth24 EndpointsREST
For Agents
Programmatically available layers, upload data to the specified layer. Covers 4 operations with oauth2 authentication.
Use for: I need to available layers, I want to upload data to the specified layer, Search for the specified layer, Find all or correct data for a specific result.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
All endpoints are only accessible via https and are located at `api.platform.com`. Limits If the request threshold for a partner is exceeded, a `429` response code will be returned. Additionally, the following header will be returned: `Retry-After` (https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). Pagination Pagination is performed via headers. Any request which returns a list may be pagi. The API exposes 4 endpoints secured with oauth2 authentication.
Install Jentic One Beta
Connect the FieldView Platform API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FieldView Platform 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fplatform.climate.com%2Fclimate" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fplatform.climate.com%2Fclimate" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 FieldView Platform API.
Available Layers
Upload data to the specified layer
Retrieve the specified layer
Update or correct data for a specific result.
Use Cases
Patterns agents use FieldView Platform API for, with concrete tasks.
★ Developer Tools Operations
Use the FieldView Platform API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including available layers, upload data to the specified layer, retrieve the specified layer.
Call GET /layers to available layers
Automated Layers Management
Automate layers operations by combining multiple FieldView Platform API endpoints. Agents can upload data to the specified layer and then retrieve the specified layer in a single workflow.
Call POST /layer/{provider}/{type} to upload data to the specified layer, then verify the result
AI Agent Integration via Jentic
AI agents discover and call FieldView Platform API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'available layers', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — all endpoints are only accessible via https and are located at `api.
METHOD
PATH
DESCRIPTION
GET
/layers
Available Layers
POST
/layer/{provider}/{type}
Upload data to the specified layer
GET
/layer/{provider}/{type}
Retrieve the specified layer
PUT
/layer/{provider}/{type}/{id}
Update or correct data for a specific result.
GET
/layers
Available Layers
POST
/layer/{provider}/{type}
Upload data to the specified layer
GET
/layer/{provider}/{type}
Retrieve the specified layer
PUT
/layer/{provider}/{type}/{id}
Update or correct data for a specific result.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the FieldView Platform API by hand means setting up its OAuth authorization-code flow and hand-building requests across its layer endpoints yourself. Through Jentic you install once, import FieldView from the API Directory, store the credential once, and your agent calls it.
Permission scoping
FieldView puts the provider, type and id in the URL path (/layer/{provider}/{type}/{id}), so a rule can pin your agent to one provider and layer type: it reads and updates layers there and nothing else. You choose the operations it may call, so state-changing ones like updating a layer are not included unless you add them.
Credential isolation
Your FieldView OAuth 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 'list available layers' or 'read a layer', and Jentic returns the matching FieldView operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using FieldView Platform API through Jentic.
What authentication does the FieldView Platform API use?
The FieldView Platform API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I available layers with the FieldView Platform API?
Yes. Use the GET /layers endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the FieldView Platform API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I available layers through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'available layers'. Jentic returns the matching FieldView Platform API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the FieldView Platform API have?
The FieldView Platform API exposes 4 endpoints covering layers operations.
Can I limit what my agent is allowed to do with the FieldView Platform API?
Yes. Jentic One is self-hosted, so your own rules decide which FieldView operations and credentials your agent can use. Because the API puts the provider, type, and id in the URL path (/layer/{provider}/{type}/{id}), you can pin the agent to a single provider and layer type and grant only reading layers with GET /layers and GET /layer/{provider}/{type}. State-changing calls like POST /layer/{provider}/{type} or PUT /layer/{provider}/{type}/{id} stay out of reach unless you add them.
GET STARTED