docs(data-governance): add EU endpoint page - #49
Conversation
Document api.eu.edenai.run: base URL, code samples, region-filtered discovery, and the 451 rejection shape for non-EU providers. Verified against live /v3/models and /v3/info on both hosts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
WalkthroughA new EU regional endpoint documentation page is introduced alongside a navigation configuration update. The documentation explains the EU endpoint's base URL, demonstrates request examples in cURL, Python, and JavaScript, describes EU-available model discovery behavior, specifies HTTP 451 error handling for unavailable providers, and lists behavioral characteristics and related topics. ChangesEU Endpoint Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@v3/data-governance/eu-endpoint.mdx`:
- Around line 26-27: Replace the literal placeholder "YOUR_API_KEY" in all curl
examples (e.g., the POST example for chat/completions and the other occurrences
noted) with the documented production placeholder format "Bearer <api_token>" so
examples use Authorization: Bearer <api_token>; also ensure any testing/sandbox
examples use "Bearer <sandbox_api_token>" where appropriate and that the header
text reads Authorization: Bearer <api_token> (or <sandbox_api_token>)
consistently across the file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 5dcf4621-c912-43c1-a1d3-45ee9fa6277d
📒 Files selected for processing (2)
docs.jsonv3/data-governance/eu-endpoint.mdx
/v3/models and /v3/info are public — the original samples carried a Bearer token that the endpoints don't require. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The earlier merge of main into this branch dropped the General, Data Governance, and Integrations groups and reassigned the EU endpoint page into Video Generation Features. Rebuild from main with just the intended single-line addition under Data Governance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
LLM endpoints wrap region rejections in the OpenAI-compatible error
envelope (error.message / error.type=request_forbidden / error.code=
region_not_allowed), not FastAPI's {"detail": {...}} shape. Document
both shapes since universal-ai still uses the FastAPI envelope.
Verified live with google/gemini-3.5-flash on api.eu.edenai.run.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Match the project-wide convention (quickstart, fallback, llm endpoints, expert-models): every code section uses Python + JavaScript + cURL in a CodeGroup, wrapped in Tabs when there are multiple endpoints. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Surface the EU endpoint with the earth-europe icon on the four pages where it's a direct conceptual sibling: both data-governance pages, and the two listing-models pages (where the regions field on each model is the discovery hook for EU availability). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 participant
Summary
v3/data-governance/eu-endpoint.mdxdocumentingapi.eu.edenai.run: base URLs, request samples, region-filtered discovery, and the HTTP 451 response shape for non-EU providers.docs.json.Covers the EDE3-389 work merged in edenai-back#2429 and aifeatures#259.
Verified against the live API
regionsfield shape on/v3/modelsand/v3/info— confirmed[{"code":"eu","name":"Europe"}].mistral/mistral-large-latestis EU-eligible (used in the Python/JS/curl sample).openai/gpt-4ois not EU-eligible (used in the 451 example) — 0 of 81 OpenAI models surface on the EU host.?region=eupreview section after live testing showed v3 endpoints readrequest.state.region(host only), not the query param —resolve_request_regionis defined inaifeaturesbut not currently wired to a route.Test plan
servers-location,data-retention,listing-modelsresolve🤖 Generated with Claude Code
Summary by CodeRabbit