| name | firecrawl-enterprise-rbac |
| description | Configure Firecrawl team access control with per-key credit limits and domain restrictions.
Use when managing multiple API keys per team, implementing credit budgets per consumer,
or controlling which domains each team can scrape.
Trigger with phrases like "firecrawl RBAC", "firecrawl teams",
"firecrawl enterprise", "firecrawl access control", "firecrawl permissions".
|
| allowed-tools | Read, Write, Edit |
| version | 1.11.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","firecrawl","rbac"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Firecrawl Enterprise RBAC
Overview
Control access to Firecrawl scraping resources through API key management, domain allowlists, and credit budgets per team. Firecrawl's credit-based pricing means access control is primarily about limiting credit consumption and restricting scrape targets per consumer.
Prerequisites
- Firecrawl Team or Scale plan
- Dashboard access at firecrawl.dev/app
- Understanding of credit-per-page billing
Instructions
Step 1: Separate API Keys per Consumer
set -euo pipefail
Step 2: Gateway Proxy with Domain Allowlists
import FirecrawlApp from "@mendable/firecrawl-js";
const TEAM_POLICIES: Record<string, {
apiKey: string;
allowedDomains: string[];
maxPagesPerCrawl: number;
dailyCreditLimit: number;
}> = {
"content-team": {
apiKey: process.env.FIRECRAWL_KEY_CONTENT!,
allowedDomains: ["docs.*", "*.readthedocs.io", "medium.com"],
maxPagesPerCrawl: ,
: ,
},
: {
: process..!,
: [, , ],
: ,
: ,
},
: {
: process..!,
: [],
: ,
: ,
},
};
(): {
policy = [team];
(!policy) ;
domain = (url).;
policy..(
pattern === || domain.(pattern.(, ).(, ))
);
}
(): {
policy = [team];
(!policy) ();
({ : policy. });
}