Should we expect the current API (https://docs.goodfire.ai/introduction) to be good for prod or is it for testing only?

I see that the sampling API is OpenAI-compatible (nice!). Considering if we can add a native integration for this to LiteLLM with a provider specific route - `goodfire/`. Would let people test this in projects like aider and dspy.

```python

from litellm import completion

import os

os.environ["GOODFIRE_API_KEY"] = "your-api-key"

response = completion( model="goodfire/meta-llama/Llama-3.3-70B-Instruct", messages=[{ "content": "Hello, how are you?","role": "user"}] )

```

I wish you could filter by startup name. Would be curious to know where we (litellm) ended up

Saw you just support claude for now. If your backend code is in Python, happy to add support for other models (OpenAI/Gemini/etc.) via a consistent API interface like LiteLLM - https://docs.litellm.ai/docs/#litellm-python-sdk

Was looking at adding this to litellm - https://docs.litellm.ai/docs/providers

but the website crashed on me while reviewing the docs. Is this stable yet?

Your changelog is neat - is this custom built or via some embeddable tool?

Interesting - how do you use LiteLLM + OpenRouter here?

I would assume they're alternatives

Just saw `from litellm import completion` code

Thank you for using litellm + all your issues on our repo! @Ey7NFZ3P0nzAe

- litellm maintainer

It's interesting to see how short-lived some of these were (e.g. HumanEval).

Interesting — does your backend server use Python? I couldn't find much about it on your site.

It would be great to see this tested with more commercial LLMs (O1 / Amazon Nova, / Llama 3.2 / etc.). If you're open to it, I’d be happy to contribute support for these models via LiteLLM - https://docs.litellm.ai/docs/providers

+1 on the github issues. It's very useful to have this on the litellm docs

nice! lmk if you have any feedback while using it in the litellm docs.