Thanks for using webfetch. Here's how to get help, ranked by speed.
- GitHub Discussions — questions, ideas, show-and-tell, and "is this a bug?" triage: https://github.com/ashlrai/webfetch/discussions
- Discord — chat with maintainers and other users: https://getwebfetch.com/discord
- Issues — for confirmed bugs and concrete feature requests, use the issue templates. Please search existing issues first.
We try to respond to community questions within a few business days, but there is no SLA on community channels.
- README — install, quick-start, architecture
docs/PROVIDERS.md— per-provider gotchas and rate limitsdocs/PROVIDER_TUNING.md— picking providers per use casedocs/LICENSE_POLICY.md— how license-first ranking works
Do not use issues, Discussions, or Discord for security reports. See SECURITY.md.
The hosted tier at getwebfetch.com includes pooled provider keys, the managed browser fallback, and team usage dashboards. See https://getwebfetch.com/pricing.
For SLAs, private deployments, custom provider work, or volume licensing, contact enterprise@getwebfetch.com.
- Self-hosted deployments where you've modified the default safety settings — we can advise but cannot prioritize fixes for custom configs.
- Forks. If you've forked, you own the support.
- Third-party MCP clients we haven't tested. We officially support Claude Code, Cursor, Cline, Continue, Roo Code, and Codex.