docs: add Requesty to the provider docs and README

[Thibaultjaigu]

Issue for this PR

None, docs only change.

Type of change

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

What does this PR do?

Requesty is already in the models.dev catalog (requesty, REQUESTY_API_KEY, @ai-sdk/openai-compatible, https://router.requesty.ai/v1), so it works today with no code changes. It just isn't mentioned in the docs.

This adds a short "Requesty" section to docs/docs/configure/providers.md right after OpenRouter, with a config example for requesty/openai/gpt-4o-mini, a note that /connect or altimate-code auth login already lists it, and the key page link. It also adds Requesty to the provider list in the README.

How did you verify your code works?

Loaded the exact config from the new docs section through Provider.list(), Provider.getModel() and Provider.getLanguage() in a throwaway bun test, then ran generateText against the live API with REQUESTY_API_KEY set. Both openai/gpt-4o-mini (declared in config) and openai/gpt-4.1-mini (catalog only, no config) returned the expected reply. The pre-push hook (bun typecheck) passed.

Screenshots / recordings

N/A

Checklist

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

Disclosure: I work at Requesty. Happy to adjust anything to match project conventions.

---

Summary by cubic

Adds Requesty to the provider docs and README. Requesty already works via the models.dev catalog with no code changes, but wasn't documented.

• Adds a Requesty section to docs/docs/configure/providers.md with a config example for requesty/openai/gpt-4o-mini.
• Notes that /connect or altimate-code auth login already lists it and that setting REQUESTY_API_KEY is enough for catalog models.
• Adds Requesty to the provider list in the README.

^{Written for commit 9c86dc6. Summary will update on new commits.}

Summary by CodeRabbit

• Documentation
  • Added Requesty to the list of supported LLM providers.
  • Added setup guidance and an example configuration for using Requesty models.

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 6bede9f5-c694-4342-8804-c5e424e82d77

📥 Commits

Reviewing files that changed from the base of the PR and between 7ed6e16 and 9c86dc6.

📒 Files selected for processing (2)

• README.md
• docs/docs/configure/providers.md

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

The README now lists Requesty as an LLM provider. The provider guide adds a Requesty configuration example and instructions for using catalog models or adding other Requesty model IDs.

Changes

Requesty provider documentation

Layer / File(s)	Summary
Requesty setup and provider listing README.md, docs/docs/configure/providers.md	The README lists Requesty. The provider guide shows an openai/gpt-4o-mini configuration and explains use of REQUESTY_API_KEY with catalog models or registration of other Requesty model IDs.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: anandgupta42

Merge Risk: ⚪ Minimal · up to 9c86d

The new Requesty setup matches the existing catalog and uses the documented API-key environment variable. No merge-blocking issue is evident; the documentation change is ready for normal checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the documentation changes for Requesty in the provider docs and README.
Description check	✅ Passed	The description includes the issue context, change type, implementation summary, verification steps, screenshot status, and completed checklist items. It provides sufficient detail for this documentat…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit reads the provider guide,
Then hops where Requesty models hide.
An API key, a model name,
The README adds them to the game.
Soft paws tap; the docs are bright.}

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

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• README.md
• docs/docs/configure/providers.md

---

_{Reviewed by gpt-sol-latest · Input: 0 · Output: 0 · Cached: 0}

_{Review guidance: REVIEW.md from base branch main}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}