Added Fireworks as a provider

[ndrewGele]

• [ x ] I have read CONTRIBUTING.md.
• [ x ] I have created a discussion that was approved by a maintainer (for new features).

Worth noting that my agent identified some discrepancies between which serverless models Fireworks advertises on their website and what their API returns, but I decided to use the API as a source of truth.
Ran it locally and asked a few of the cheaper models to write fizzbuzz for me as a test.

[meowgorithm]

Thanks for the quick PR @ndrewGele! AFAIK, Fireworks has support for OpenAI and Anthropic-compatible endpoints, so we should be able to add this in without any Go code.

I think it also supports newer formats like the Responses API, but up to @andreynering which of these is the right shape.

[ndrewGele]

I'll take a look at the linter issues later today.

[ndrewGele]

Thanks for the quick PR @ndrewGele! AFAIK, Fireworks has support for OpenAI and Anthropic-compatible endpoints, so we should be able to add this in without any Go code.

I think it also supports newer formats like the Responses API, but up to @andreynering which of these is the right shape.

Hey, missed this reply earlier, but thanks for the quick review on your end as well!
It sounds like there's a preference to keep things simply defined in the JSON over adding scrapers? If so, the new commits should address that.
Also noticed that a binary got committed initially, so I killed that with the force push.

[andreynering]

Hi @ndrewGele,

Some notes:

• I'd say we should use the OpenAI-compat endpoint as a default, unless we have reasons to believe the Anthropic-compatible one works better.
• If this provider has a public /models endpoint, having a generator is prefferable. That means we'll be updating the list daily.

[andreynering]

They have a /models endpoint, but it requires authentication. Would still be useful, tho.