Skip to content

docs: add Eden AI integration guides for Bifrost and Lynkr (AI Gateway)#73

Merged
MVS-source merged 2 commits into
mainfrom
integrations/bifrost-lynkr
Jul 17, 2026
Merged

docs: add Eden AI integration guides for Bifrost and Lynkr (AI Gateway)#73
MVS-source merged 2 commits into
mainfrom
integrations/bifrost-lynkr

Conversation

@MVS-source

Copy link
Copy Markdown
Collaborator

What

Two new integration guides, grouped under a new AI Gateway nav section:

Guide Type Integration path
Bifrost OpenAI-compatible LLM gateway (Go) Custom Provider in config.json, no fork/build
Lynkr Tier-based routing gateway Eden AI is a built-in provider

Both route to Eden AI's OpenAI-compatible V3 API (https://api.edenai.run/v3).

Files

  • v3/integrations/bifrost.mdx, v3/integrations/lynkr.mdx (new)
  • integration-logo/bifrost-icondoc.svg, lynkr-icondoc.svg (new, square marks)
  • docs.json — new AI Gateway group (icon network-wired)

Conventions

  • Format matches existing integration docs (<TechArticleSchema> + <CodeGroup>).
  • Env var: EDEN_AI_API_KEY (house style) for Bifrost; EDENAI_API_KEY for Lynkr (derives <PROVIDER>_API_KEY).

To confirm before merge

  • Bifrost custom_provider_config.allowed_requests keys vs the current Bifrost schema.
  • Lynkr TIER_* names and default port (8081).

Add two new integration guides under a new "AI Gateway" nav group:

- Bifrost: OpenAI-compatible LLM gateway (Custom Provider config)
- Lynkr: tier-based routing gateway (built-in Eden AI provider)

Both point at https://api.edenai.run/v3. Env var follows the docs house
style (EDEN_AI_API_KEY) for Bifrost; Lynkr uses its derived
EDENAI_API_KEY (<PROVIDER>_API_KEY convention). Includes square icon SVGs
and docs.json nav entries.
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@MVS-source, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 03eff52e-d0e9-4ce1-a730-3da4ff3cab18

📥 Commits

Reviewing files that changed from the base of the PR and between 5174e81 and 5f26b09.

⛔ Files ignored due to path filters (2)
  • integration-logo/bifrost-icondoc.svg is excluded by !**/*.svg
  • integration-logo/lynkr-icondoc.svg is excluded by !**/*.svg
📒 Files selected for processing (3)
  • docs.json
  • v3/integrations/bifrost.mdx
  • v3/integrations/lynkr.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch integrations/bifrost-lynkr

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mintlify

mintlify Bot commented Jul 16, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
edenai 🟢 Ready View Preview Jul 16, 2026, 3:38 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@mintlify

mintlify Bot commented Jul 16, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
edenai 🟡 Building Jul 16, 2026, 3:36 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@MVS-source
MVS-source merged commit a0743c4 into main Jul 17, 2026
6 checks passed
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.

2 participants