Skip to content

Add Lightning Rod provider and Foresight v4 model#3350

Open
bartolomej wants to merge 2 commits into
anomalyco:devfrom
lightning-rod-labs:lightningrod-provider-models
Open

Add Lightning Rod provider and Foresight v4 model#3350
bartolomej wants to merge 2 commits into
anomalyco:devfrom
lightning-rod-labs:lightningrod-provider-models

Conversation

@bartolomej

Copy link
Copy Markdown

Add Lightning Rod Labs provider with Foresight v4

Summary

  • Add providers/lightningrod/ with provider metadata and Foresight v4 model definition

What was added

  • providers/lightningrod/provider.toml — OpenAI-compatible provider at https://api.lightningrod.ai/v1/openai
  • providers/lightningrod/models/foresight-v4.toml — specialized AI forecasting model

Data source

Validation

  • Ran: bun validate
  • Result: passes

@github-actions

Copy link
Copy Markdown
Contributor

Action items

  • [critical] [violation] providers/lightningrod/models/foresight-v4.toml:1 - Check: ModelBase (packages/core/src/schema.ts:217) requires a non-empty description string for every provider model authored inline (without base_model). Why: The new TOML omits description, so AuthoredModel.safeParse in generate.ts will throw "Required" for this field and bun validate will exit non-zero, contradicting the PR body's "Result: passes" claim. Every inline provider model in the repo includes this field (e.g. providers/stepfun-step-plan/models/step-router-v1.toml:2, providers/bailing/models/Ring-1T.toml:2). Action: Add a description = "..." line directly after name with a concise, non-empty model description.
  • [low] [possible mistake] providers/lightningrod/models/foresight-v4.toml:6 - Check: reasoning_options must reflect the provider's actual API surface, and data-changing PRs should map each citation to the specific claim it supports. Why: The PR declares effort with ["low", "medium", "high"] for a niche provider, but the PR body's two URLs (https://www.lightningrod.ai/models, https://docs.lightningrod.ai) are not mapped to specific claims, so the reasoning_effort support, accepted values, pricing, and limits cannot be reviewed from the PR. Action: Cite the specific documentation page that confirms Lightning Rod's reasoning_effort parameter and its accepted values (and the cost/limit figures), or set reasoning_options = [] if no caller control is verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant