Skip to content

docs: document Requesty OpenAI-compatible gateway setup - #3391

Open
Thibaultjaigu wants to merge 1 commit into
ultraworkers:mainfrom
thibault-forks:add-requesty-provider
Open

Thibaultjaigu wants to merge 1 commit into
ultraworkers:mainfrom
thibault-forks:add-requesty-provider

Conversation

@Thibaultjaigu

Copy link
Copy Markdown

Summary

  • Adds a Requesty section to docs/local-openai-compatible-providers.md, after the HopBase section. Docs only.
  • Covers the base URL (global and EU) and key, using local/<catalog id> for vendor-prefixed ids, and the native Anthropic route through ANTHROPIC_BASE_URL=https://router.requesty.ai.
  • Requesty routes requests to first party providers (OpenAI, Anthropic, Google and others) rather than resellers.

Anti-slop triage

  • Classification: docs-only
  • Evidence: release binary v0.1.13 (claw-macos-arm64, sha256 checked) with a real Requesty key and an empty CLAW_CONFIG_HOME. With OPENAI_BASE_URL=https://router.requesty.ai/v1, claw --model <id> prompt "Reply exactly HELLO_WORLD_123" printed HELLO_WORLD_123 for openai/gpt-4o-mini, local/anthropic/claude-sonnet-5-5 and local/google/gemini-3.6-flash. With ANTHROPIC_BASE_URL=https://router.requesty.ai and ANTHROPIC_API_KEY set to the Requesty key, --model anthropic/claude-sonnet-5-5 printed the same. A bare anthropic/claude-sonnet-5-5 with only the OpenAI variables set failed with missing Anthropic credentials, as the section says.
  • Non-destructive review result: merge candidate

Verification

  • python .github/scripts/check_doc_source_of_truth.py and check_release_readiness.py pass. No Rust code changed, so cargo test wasn't run; I tested with the published release binary rather than a local build.
  • git diff --check passes.
  • No live secrets, tokens, private logs, or unrelated generated churn are included. The keyless curl ... | jq model list command in the section was run as written (750 ids today).

Resolution gate

  • If this PR resolves an issue, the issue number and fix evidence are linked. (No issue, docs addition only.)
  • If this PR should not merge, the rejection/defer rationale is evidence-backed and does not rely on vibes.
  • I did not merge/close remote PRs or issues from an automation lane without owner approval.

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

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.

1 participant