canonical: https://jentic.com/apis/solcast.com.au/solcast-com-au

# Solcast API

Solcast provides forecast, live, and historical solar irradiance, PV power, and weather data. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically get radiation forecasts, get radiation estimated actuals. Covers 5 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for data enrichment only.

## Capabilities

- Get radiation forecasts
- Manage data enrichment data programmatically
- Integrate Solcast API into automated workflows
- Query and filter Solcast API records by parameters
- Monitor Solcast API operational status and events

## Use cases

### Data Enrichment Operations

Use the Solcast API to perform data enrichment operations programmatically. The API provides 5 endpoints covering core functionality including get radiation forecasts, get radiation estimated actuals, get pv power forecasts.

Example prompt: Call GET `/world_radiation/forecasts` to get radiation forecasts

### Automated PV Power Management

Automate pv power operations by combining multiple Solcast API endpoints. Agents can get radiation estimated actuals and then get pv power forecasts in a single workflow.

Example prompt: Call GET `/world_radiation/estimated_actuals` to get radiation estimated actuals, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Solcast 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 bearer tokens manually.

Example prompt: Search Jentic for 'get radiation forecasts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/world_radiation/forecasts` | Get radiation forecasts |
| GET | `/world_radiation/estimated_actuals` | Get radiation estimated actuals |
| GET | `/world_pv_power/forecasts` | Get PV power forecasts |
| GET | `/world_pv_power/estimated_actuals` | Get PV power estimated actuals |
| GET | `/tmy_hourly` | Get TMY hourly data |

## Key resources

- **PV Power** — Operations related to PV Power
- **Radiation** — Operations related to Radiation
- **TMY** — Operations related to TMY

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/solcast.com.au/solcast-com-au/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Clearbit** — Alternative data enrichment API
- **Fullcontact** — Alternative data enrichment API
- **Hunter** — Complementary data enrichment API

## FAQ

### What authentication does the Solcast API use?

The Solcast API uses a Bearer token in the Authorization header. 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 get radiation forecasts with the Solcast API?

Yes. Use the GET `/world_radiation/forecasts` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Solcast 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 get radiation forecasts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get radiation forecasts'. Jentic returns the matching Solcast API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Solcast API have?

The Solcast API exposes 5 endpoints covering pv power, radiation, tmy operations.

### Can I limit what my agent is allowed to do with the Solcast API?

Yes. Because you run Jentic One yourself, you decide which Solcast operations sit in your agent's allowed set, and anything you do not add stays out of reach. The Solcast API is read-only and scoped through query parameters rather than resource IDs in the path, so you can permit just the calls the agent needs, such as fetching world radiation forecasts or estimated actuals while leaving PV power forecasts and TMY hourly data out. Your bearer token is held by your own instance and injected only when an allowed operation runs, never in the agent's prompt or logs.