TROLIE

TROLIE (Transmission Ratings and Operating Limits Information Exchange) is an open-source LF Energy project, hosted under LF Projects, that defines an OpenAPI-based REST specification for exchanging transmission facility ratings and operating limits. It responds to FERC Order 881, which requires North American Transmission Owners, Transmission Operators, Transmission Providers and Reliability Coordinators to exchange ambient-adjusted and forecasted ratings. The project publishes the 1.0 specification, usage examples for forecast, real-time, seasonal and temporary ratings, decision records, a conformance suite and a Java client SDK on GitHub.

TROLIE publishes 6 API contracts indexed on the APIs.io network, including Forecasting API, Monitoring Sets API, Seasonal API, and 3 more. Tagged areas include Company, Energy, Electric Grid, Transmission, and Open Standards.

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

TROLIE’s developer surface includes changelog, authentication, API reference, getting-started guide, FAQ, engineering blog, support, and 28 more developer resources.

43.3/100 developing Agent 40/100 agent ready Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0
2 published contracts
CompanyEnergyElectric GridTransmissionOpen StandardsOpenAPILF EnergyOpen Source

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
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/trolie: 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 6

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

TROLIE Forecasting API

The Forecasting API operations define the exchange of forecasted ratings, including the 240-hour-ahead forecasted AAR data exchange required by FERC Order 881. The operations su...

TROLIE Monitoring Sets API

[Monitoring Sets](https://trolie.energy/concepts#monitoring-sets) are named sets of power system resources that may be used to filter ratings and limits returned by queries agai...

TROLIE Seasonal API

Seasonal ratings are static ratings associated with extended durations, typically months. These are typically used in both planning and operations. Power system resources that a...

TROLIE Seasonal Overrides API

A Seasonal Override instructs the system to use a temporary static rating instead of any concurrent Seasonal Rating for a resource. A typical use case is a so-called 'de-rate' d...

TROLIE Temporary AAR Exceptions API

A [Temporary AAR Exception](https://trolie.energy/concepts#temporary-aar-exception) is provided by the Ratings Provider when a Ratings Obligation cannot be fulfilled, due to som...

TROLIE Realtime API

If permitted by the Clearinghouse Provider, its Ratings Providers can use these functions to exchange real-time ratings, supplementing or replacing traditional telemetry protoco...

Pricing Plans 1

Published pricing tiers and plan structures.

Trolie Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Trolie Rate Limits

0 limits

RATE LIMITS

Semantic Vocabularies 1

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

Trolie Context

81 classes · 57 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

TROLIE API Rules

16 rules · 14 errors 1 warnings 1 info

SPECTRAL

TROLIE API Rules

5 rules · 5 warnings

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Trolie Openapi Overlay

29 actions · update · trolie-openapi.yml

GENERATED

JSON Schema 6

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

forecast-proposal-status

6 properties

JSON SCHEMA

real-time-proposal-status

5 properties

JSON SCHEMA

realtime-proposal

3 properties

JSON SCHEMA

seasonal-ratings-proposal-status

5 properties

JSON SCHEMA

Examples 5

Example request and response payloads for these APIs.

Security Posture 2

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

Trolie Authentication

oauth2 · 1 scheme

SECURITY

Trolie Domain Security

TLSv1.3 · HSTS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Trolie Scopes

15 scopes · clientCredentials

15 scopes

SCOPES

Agentic Access 1

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

Trolie Agentic Access

28 operations · 13 acting · 3 human-in-the-loop

28 operations · 13 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 10

Pagination, idempotency, versioning, errors, and events

Scroll for all 10

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Company 2

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: trolie
name: TROLIE
description: TROLIE (Transmission Ratings and Operating Limits Information Exchange) is an open-source LF Energy project,
  hosted under LF Projects, that defines an OpenAPI-based REST specification for exchanging transmission facility ratings
  and operating limits. It responds to FERC Order 881, which requires North American Transmission Owners, Transmission Operators,
  Transmission Providers and Reliability Coordinators to exchange ambient-adjusted and forecasted ratings. The project publishes
  the 1.0 specification, usage examples for forecast, real-time, seasonal and temporary ratings, decision records, a conformance
  suite and a Java client SDK on GitHub.
url: https://raw.githubusercontent.com/api-evangelist/trolie/refs/heads/main/apis.yml
x-type: company
x-source: harvest:spectral-ruleset-github
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-09 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-09'
modified: '2026-10-09'
tags:
- Company
- Energy
- Electric Grid
- Transmission
- Open Standards
- OpenAPI
- LF Energy
- Open Source
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
image: https://trolie.energy/images/TROLIE-icon-white.svg
common:
- type: AgenticAccess
  url: agentic-access/trolie-agentic-access.yml
- type: Spectral
  url: rules/trolie-spec-spectral-rules.yml
- type: Spectral
  url: rules/trolie-rules.yml
- type: JSONLD
  url: json-ld/trolie-context.jsonld
- type: Vocabulary
  url: vocabulary/trolie-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DataModel
  url: data-model/trolie-data-model.yml
- type: ChangeLog
  url: changelog/trolie-changelog.yml
- type: Conventions
  url: conventions/trolie-conventions.yml
- type: Deprecation
  url: lifecycle/trolie-lifecycle.yml
- type: Lifecycle
  url: lifecycle/trolie-lifecycle.yml
- type: ErrorCatalog
  url: errors/trolie-problem-types.yml
- type: Conformance
  url: conformance/trolie-conformance.yml
- type: Overlay
  url: overlays/trolie-openapi-overlay.yaml
- type: WellKnown
  url: well-known/trolie-well-known.yml
- type: Hosts
  url: hosts/trolie-hosts.yml
- type: Vendors
  url: vendors/trolie-vendors.yml
- type: SDKs
  url: packages/trolie-packages.yml
- type: Packages
  url: packages/trolie-packages.yml
- type: Authentication
  url: authentication/trolie-authentication.yml
- type: OAuthScopes
  url: scopes/trolie-scopes.yml
- type: DomainSecurity
  url: security/trolie-domain-security.yml
- type: Website
  url: https://trolie.energy/
- type: SpectralRules
  url: https://github.com/trolie/spec/blob/39741d03365cb430ab5d7e677312759a7f4a6d14/.spectral.yaml
- type: APIReference
  url: https://trolie.energy/spec-1.0
- type: GettingStarted
  url: https://trolie.energy/concepts.html
- type: UsageExamples
  url: https://trolie.energy/usage-examples.html
- type: FAQ
  url: https://trolie.energy/faq.html
- type: Blog
  url: https://trolie.energy/community_events.html
- type: GitHubOrganization
  url: https://github.com/trolie
- type: GitHubRepository
  url: https://github.com/TROLIE/spec
- type: ChangeLog
  url: https://github.com/trolie/spec/releases
- type: Issues
  url: https://github.com/trolie/spec/issues
- type: Support
  url: https://lists.lfenergy.org/g/trolie-general
- type: Foundation
  url: https://lfenergy.org/projects/trolie/
apis:
- aid: trolie:trolie-forecasting-api
  name: TROLIE Forecasting API
  description: 'The Forecasting API operations define the exchange of forecasted ratings,

    including the 240-hour-ahead forecasted AAR data exchange required by FERC

    Order 881.  The operations support submitting rating proposals, querying

    in-use limits, and monitoring the health and validity of submissions

    against the Rating Provider''s obligations.'
  humanURL: https://trolie.energy/spec-1.0
  tags:
  - Forecasting
  properties:
  - type: OpenAPI
    url: openapi/trolie-forecasting-api-openapi.yml
  - type: Documentation
    url: https://trolie.energy/spec-1.0
  - type: JSONSchema
    url: json-schema/trolie-forecast-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-real-time-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-seasonal-ratings-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-proposal-schema.json
  - type: JSONSchema
    url: json-schema/trolie-forecast-limits-snapshot-slim-inputs-used-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-limits-snapshot-slim-inputs-used-schema.json
- aid: trolie:trolie-monitoring-sets-api
  name: TROLIE Monitoring Sets API
  description: '[Monitoring Sets](https://trolie.energy/concepts#monitoring-sets) are

    named sets of power system resources that may be used to filter ratings

    and limits returned by queries against these APIs. How Monitoring Sets are

    defined is beyond the scope of the TROLIE specification, and it is assumed

    that the sender and receiver have predefined the appropriate Monitoring

    Sets.'
  humanURL: https://trolie.energy/spec-1.0
  tags:
  - Monitoring Sets
  properties:
  - type: OpenAPI
    url: openapi/trolie-monitoring-sets-api-openapi.yml
  - type: Documentation
    url: https://trolie.energy/spec-1.0
  - type: JSONSchema
    url: json-schema/trolie-forecast-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-real-time-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-seasonal-ratings-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-proposal-schema.json
  - type: JSONSchema
    url: json-schema/trolie-forecast-limits-snapshot-slim-inputs-used-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-limits-snapshot-slim-inputs-used-schema.json
- aid: trolie:trolie-seasonal-api
  name: TROLIE Seasonal API
  description: 'Seasonal ratings are static ratings associated with extended durations,

    typically months. These are typically used in both planning and

    operations.


    Power system resources that are exempt from providing AARs generally

    operate at a seasonal rating. Even for resources using dynamic ratings, a

    seasonal rating is still necessary. This acts as a recourse when a dynamic

    rating is unavailable.  For example, a dynamic rating

    might be unavailable during communication outages or for forecasts beyond

    the ten-day period required by FERC Order 881.'
  humanURL: https://trolie.energy/spec-1.0
  tags:
  - Seasonal
  properties:
  - type: OpenAPI
    url: openapi/trolie-seasonal-api-openapi.yml
  - type: Documentation
    url: https://trolie.energy/spec-1.0
  - type: JSONSchema
    url: json-schema/trolie-forecast-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-real-time-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-seasonal-ratings-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-proposal-schema.json
  - type: JSONSchema
    url: json-schema/trolie-forecast-limits-snapshot-slim-inputs-used-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-limits-snapshot-slim-inputs-used-schema.json
- aid: trolie:trolie-seasonal-overrides-api
  name: TROLIE Seasonal Overrides API
  description: 'A Seasonal Override instructs the system to use a temporary static rating

    instead of any concurrent Seasonal Rating for a resource.


    A typical use case is a so-called ''de-rate'' due to a temporary clearance

    issue for a transmission facility that is exempt from providing AARs.


    Exempt facilities typically operate at a seasonal rating. However, instead

    of updating the seasonal rating schedule, a Ratings Provider can send a

    Seasonal Override.


    During the override period, the Clearinghouse uses the Seasonal

    Override rating instead of any scheduled seasonal ratings.


    For resources required to provide AARs, a Ratings Provider would issue a

    Temporary AAR Exception to address temporary conditions requiring a static

    rating.'
  humanURL: https://trolie.energy/spec-1.0
  tags:
  - Seasonal Overrides
  properties:
  - type: OpenAPI
    url: openapi/trolie-seasonal-overrides-api-openapi.yml
  - type: Documentation
    url: https://trolie.energy/spec-1.0
  - type: JSONSchema
    url: json-schema/trolie-forecast-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-real-time-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-seasonal-ratings-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-proposal-schema.json
  - type: JSONSchema
    url: json-schema/trolie-forecast-limits-snapshot-slim-inputs-used-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-limits-snapshot-slim-inputs-used-schema.json
- aid: trolie:trolie-temporary-aar-exceptions-api
  name: TROLIE Temporary AAR Exceptions API
  description: "A [Temporary AAR Exception](https://trolie.energy/concepts#temporary-aar-exception) is\nprovided by the Ratings\
    \ Provider when a Ratings Obligation cannot be\nfulfilled, due to some temporary operating condition impacting the related\n\
    power system resource.  This could occur in various scenarios:\n\n  * An equipment failure.\n  * An unforeseen condition\
    \ on a related part of the power grid.\n  * Some ambient condition that is not part of the model is heating the\n    line,\
    \ like a wildfire.\n  * Something in the surrounding environment is affecting the amount that a\n    line is allowed to\
    \ sag. For example, this may occur for lines over\n    rivers when very large ships pass under them\n\nA Temporary AAR\
    \ Exception serves two main purposes: documenting the reason\nfor the exception and providing a temporary rating value\
    \ set. It is employed\nin three distinct circumstances:\n\n1. Firstly, Order 881 mandates documentation and archival of\
    \ all use of\n alternate ratings in lieu of AARs. Ratings Providers should continue to\n provide real-time and forecast\
    \ ratings for the affected resource, but\n these should match the rating provided with the Temporary AAR Exception\n while\
    \ the latter is in effect. This temporary rating, and the reason that\n it occurred, must be captured in history regardless\
    \ of the provided\n ratings.  The reason and the end date of the effective window may be\n updated after the object has\
    \ been created, up to a configurable threshold.\n\n   If the Ratings Providers provides ratings that deviate from the\
    \ static\n   Temporary AAR Exception rating, the Clearinghouse Provider must decide\n   whether to use those or the static\
    \ rating. The Clearinghouse Provider\n   advise its Ratings Providers on how it will choose ahead of time. This\n   specification\
    \ recommends using the dynamic rating provided, but it does\n   not mandate it.\n\n2. Secondly, Temporary AAR Exceptions\
    \ apply when the Clearinghouse\n  Provider is generating forecast rating proposals on behalf of the Ratings Provider,\
    \ e.g., when lookup tables are provided ahead of time by the Ratings Provider.\n  Since there is no external ratings,\
    \ the Clearinghouse Provider\n  wouldn't otherwise know that a temporary static rating is needed. \n\n3. Finally, for\
    \ facilities where dynamic ratings are provided, it is\n  possible that a communications outage or other issue could prevent\
    \ the\n  Clearinghouse Provider from receiving the dynamic ratings. In this case,\n  the Clearinghouse Provider would\
    \ use a Temporary AAR Exception rating."
  humanURL: https://trolie.energy/spec-1.0
  tags:
  - Temporary AAR Exceptions
  properties:
  - type: OpenAPI
    url: openapi/trolie-temporary-aar-exceptions-api-openapi.yml
  - type: Documentation
    url: https://trolie.energy/spec-1.0
  - type: JSONSchema
    url: json-schema/trolie-forecast-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-real-time-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-seasonal-ratings-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-proposal-schema.json
  - type: JSONSchema
    url: json-schema/trolie-forecast-limits-snapshot-slim-inputs-used-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-limits-snapshot-slim-inputs-used-schema.json
- aid: trolie:trolie-realtime-api
  name: TROLIE Realtime API
  description: 'If permitted by the Clearinghouse Provider, its Ratings Providers can use

    these functions to exchange real-time ratings, supplementing or replacing

    traditional telemetry protocols like ICCP.'
  humanURL: https://trolie.energy/spec-1.0
  tags:
  - Realtime
  properties:
  - type: OpenAPI
    url: openapi/trolie-realtime-api-openapi.yml
  - type: Documentation
    url: https://trolie.energy/spec-1.0
  - type: JSONSchema
    url: json-schema/trolie-forecast-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-real-time-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-seasonal-ratings-proposal-status-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-proposal-schema.json
  - type: JSONSchema
    url: json-schema/trolie-forecast-limits-snapshot-slim-inputs-used-schema.json
  - type: JSONSchema
    url: json-schema/trolie-realtime-limits-snapshot-slim-inputs-used-schema.json
x-enrichment:
  date: '2026-10-09'
  status: enriched
  artifacts_added: 43
  pass: modular-v1
  engine: identity=anthropic,contract=anthropic,surfaces=anthropic,docs=anthropic,regulatory=anthropic

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/trolie"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/trolie/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/trolie/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.

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