Support
Stuck? We're a small team that responds fast. Pick the channel that fits — most issues get resolved within a few hours.
Channels
Email
[email protected] — best for account-specific issues, billing, and bug reports.
GitHub
SDK bugs, MCP server issues, feature requests. Public and trackable.
Live chat
In the dashboard. Business hours response, fastest for time-sensitive issues.
Status page
Real-time uptime and incident history. Subscribe to alerts here.
Before you write us
The fastest support tickets are the ones that include enough context for us to reproduce the issue without asking. Please include:
- The full request URL (with token redacted to
YOUR_TOKEN) and any headers you set. - The full response — body, status code, and the
pc_status/original_statusheaders. - The
ridif one was returned. Lets us trace the request through our logs immediately. - What you expected to happen versus what actually happened.
- Whether it's reproducible — every time, intermittent, or one-off.
Response times
| Plan | Email response SLA | Live chat |
|---|---|---|
| Free / Trial | 2 business days | — |
| Pro | 1 business day | Business hours |
| Business | 4 business hours | Extended hours |
| Enterprise | 1 business hour, 24/7 critical | 24/7 + Slack channel |
What we can't help with
- "Bypass site X." If a site explicitly blocks crawling in their ToS, we won't help work around that. Crawlbase is for legitimate web data collection.
- Custom scraper requests with no volume. If you need a one-off page parsed, write your own selector. We build new scrapers when there's broader demand.
- Legal interpretation. We can't advise on whether your specific use case is compliant with GDPR / CCPA / target site ToS — talk to your lawyer.