Skip to content

docs: add Eden AI to the providers list - #43386

Open
MVS-source wants to merge 2 commits into
anomalyco:devfrom
MVS-source:docs-add-edenai-provider
Open

docs: add Eden AI to the providers list#43386
MVS-source wants to merge 2 commits into
anomalyco:devfrom
MVS-source:docs-add-edenai-provider

Conversation

@MVS-source

Copy link
Copy Markdown

Issue for this PR

Closes # N/A — docs-only. Provider registration was anomalyco/models.dev#4506 (merged 2026-08-12).

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

Adds an Eden AI section to docs/providers, between DigitalOcean and FrogBot.

Eden AI has been in models.dev since #4506 merged, and the catalog is kept current by
the sync workflow there, so it already shows up in /connect and /models. The
providers page is maintained by hand, so it was missing there. Same four steps as the
neighbouring sections.

Two notes I did add, because they are the two things people get wrong with this one:
Eden AI model ids already contain a vendor segment, so a full reference has three
segments (edenai/anthropic/claude-sonnet-5), and the EU endpoint is a different host
rather than a flag, so I showed it with the baseURL option from the Base URL section
at the top of the page.

English only. I left the 17 translated copies of providers.mdx alone since
docs-locale-sync.yml looks like it handles those separately, and they are already
behind. Happy to include them if you would rather.

For context, there was an earlier docs PR for this provider, #19089, which was declined
because at the time it documented a provider that was not in models.dev yet. That part
is now done, which is why I am back with docs only and no code. Per CONTRIBUTING, a
provider like this one needs no changes in provider.ts.

How did you verify your code works?

  • Diff is +46 −0 in one file, purely additive, no other section touched.
  • Confirmed Eden AI actually resolves before documenting it: edenai is in
    models.opencode.ai/api.json with 234 models, api and npm populated. That is the
    default source in packages/core/src/models-dev.ts, so it is what a client fetches.
  • The two models named in step 4 both respond on the live API, and both are in the
    catalog above under those display names (Mistral Large 3, Claude Sonnet 5).
  • The baseURL in step 5 was exercised: same request against
    https://api.eu.edenai.run/v3 returns 200.
  • All four links in the section return 200.
  • Compiled the edited file with @mdx-js/mdx v3, parses clean.

I did not run a full Astro build; the addition is markdown plus one fenced JSON block,
structurally identical to the OpenRouter section.

Screenshots / recordings

N/A — text-only docs change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

I work at Eden AI.

Eden AI has been in the models.dev catalog since anomalyco/models.dev#4506
merged, so it already resolves through /connect and /models. The providers page
is maintained by hand, so it was missing there.
Adds the section between DigitalOcean and FrogBot, following the same four steps
as its neighbours, plus two notes specific to this gateway: model ids carry a
vendor segment of their own, so a full reference has three segments, and the
separate EU endpoint is set through the documented baseURL option.
@Enough1122

Copy link
Copy Markdown

AI code review — automated review for reference; please use your judgment.

Reviewed by reviewer-g (AI automated review).

No blocking issues found.

  • nit: packages/web/src/content/docs/providers.mdx:880 — step 5 shows overriding baseURL to the EU gateway without ever stating the default endpoint, so readers cannot see what they are changing from; adding the global default URL (e.g. https://api.edenai.run/v3) next to the example would make the override self-explanatory.

Step 5 showed the EU base URL without ever naming the global one, so a
reader could not see what the override was changing from.
It also read as though switching hosts were free. It is not: the EU
endpoint serves the subset of the catalog available in the EU, so a
model picked in step 4 can come back as region_not_allowed there. Said
in prose rather than as a count, since the catalogs move daily.
@MVS-source

Copy link
Copy Markdown
Author

Addressed the nit in 3b86442.

Step 5 now names the global endpoint next to the override, so it is clear what is being changed from.

While I was in there I added a second sentence, because the step read as though switching hosts were free and it is not: the EU endpoint serves the subset of the catalog available in the EU, so a model picked in step 4 can come back as region_not_allowed there. I put that in prose rather than as a model count, since both catalogs move daily.

Sign up for freeto 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.

2 participants

@MVS-source@Enough1122