Solcast API

Setup

Wiring the Solcast API by hand means setting up its bearer auth, pointing at the api.solcast.com.au host, and handling paging and retries on the radiation and PV power forecast calls yourself. Through Jentic you install once, import the Solcast API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Solcast API is read-only over query parameters rather than resource ids in the URL path, so scope the agent to the operations it needs, such as fetching world radiation forecasts or estimated actuals. You choose which operations are in the allowed set, so anything you do not add stays out of reach.

Credential isolation

Your Solcast token 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 'get radiation forecasts' or 'get PV power estimated actuals', and Jentic returns the matching Solcast operation with its input schema so the agent calls the right endpoint without browsing the reference docs.