Receive, verify, deduplicate, process, and reconcile current Firecrawl crawl, batch, extract, agent, and monitor webhooks. Use when building asynchronous event delivery. Trigger with "Firecrawl webhook", "X-Firecrawl-Signature", or "Firecrawl events".

Design and audit Firecrawl team roles, API-key ownership, endpoint and format restrictions, IP restrictions, SSO, and separation of duties. Use when governing enterprise access. Trigger with "Firecrawl RBAC", "restrict a Firecrawl key", or "Firecrawl enterprise controls".

Deploy a Firecrawl v2 client integration or a reviewed self-hosted stack with secrets, canaries, health evidence, and rollback controls. Use when releasing Firecrawl-backed services. Trigger with "deploy Firecrawl", "Firecrawl production rollout", or "self-host Firecrawl".

Validate, minimize, classify, deduplicate, retain, and dispose of Firecrawl documents and extracted JSON safely. Use when building downstream storage, RAG, or analytics pipelines. Trigger with "store Firecrawl data", "Firecrawl RAG ingestion", or "clean scraped content".

Measure and reduce Firecrawl credit consumption using explicit limits, endpoint selection, cache policy, format discipline, and spend controls. Use when forecasting or correcting Firecrawl spend. Trigger with "Firecrawl costs", "reduce Firecrawl credits", or "Firecrawl budget".

Combine Firecrawl v2 map, search, batch scrape, parse, and structured JSON extraction into a governed acquisition workflow. Use when the URL set is unknown or typed data is required. Trigger with "Firecrawl map", "Firecrawl batch", "structured Firecrawl extraction", or "parse a file".

Analyze and resolve current Firecrawl v2 validation, authentication, credit, policy, rate, concurrency, timeout, and server errors. Use when an API or SDK call fails. Trigger with "Firecrawl error", "Firecrawl 429", "Firecrawl 402", or "Firecrawl forbidden".

Select a Firecrawl v2 architecture for interactive scrape, governed batch, scheduled crawl, search enrichment, or self-hosted processing. Use when designing or reviewing a Firecrawl system. Trigger with "Firecrawl architecture", "design a crawl pipeline", or "cloud versus self-hosted Firecrawl".

Isolate difficult Firecrawl v2 failures by separating caller, authentication, request, queue, rendering, origin, and result-processing evidence. Use when routine fixes fail or results are empty, partial, slow, or inconsistent. Trigger with "debug Firecrawl deeply", "empty Firecrawl result", or "stuck Firecrawl job".

Receive Exa Monitor events through verified signatures, replay resistance, deduplication, and fast acknowledgment. Use when operating or reviewing this Exa boundary. Trigger with "Exa webhooks events", "review Exa webhooks events", or "fix Exa webhooks events".

Upgrade Exa SDK or API usage through a contract inventory, fixture diff, canary, and reversible dependency change. Use when operating or reviewing this Exa boundary. Trigger with "Exa upgrade migration", "review Exa upgrade migration", or "fix Exa upgrade migration".

Isolate exa-js or exa-py behind an application-owned adapter that preserves current request semantics and safe evidence. Use when operating or reviewing this Exa boundary. Trigger with "Exa sdk patterns", "review Exa sdk patterns", or "fix Exa sdk patterns".

Design an Exa architecture that separates query policy, retrieval, content handling, asynchronous state, citations, and evidence. Use when operating or reviewing this Exa boundary. Trigger with "Exa reference architecture", "review Exa reference architecture", or "fix Exa reference architecture".

Budget Exa throughput per endpoint and distinguish caller rate limiting from vendor overload and billing exhaustion. Use when operating or reviewing this Exa boundary. Trigger with "Exa rate limits", "review Exa rate limits", or "fix Exa rate limits".

Instrument Exa calls with content-free metrics, traces, cost, and asynchronous lifecycle signals that support diagnosis without logging retrieved text. Use when operating or reviewing this Exa boundary. Trigger with "Exa observability", "review Exa observability", or "fix Exa observability".

Separate Exa development, staging, and production credentials, budgets, schedules, data, and observability. Use when operating or reviewing this Exa boundary. Trigger with "Exa multi env setup", "review Exa multi env setup", or "fix Exa multi env setup".

Build and test an Exa adapter locally using schema fixtures, recorded content-free envelopes, and an explicit opt-in live lane. Use when operating or reviewing this Exa boundary. Trigger with "Exa local dev loop", "review Exa local dev loop", or "fix Exa local dev loop".

Validate Exa capacity with synthetic workload models, endpoint-specific budgets, bounded queues, and stop conditions. Use when operating or reviewing this Exa boundary. Trigger with "Exa load scale", "review Exa load scale", or "fix Exa load scale".

Audit an Exa integration for stale search types, unsafe secrets, ignored partial failures, unbounded content work, weak citations, and orphaned asynchronous resources. Use when operating or reviewing this Exa boundary. Trigger with "Exa known pitfalls", "review Exa known pitfalls", or "fix Exa known pitfalls".

Contain Exa credential, data, cost, capacity, or correctness incidents while preserving safe evidence and vendor request IDs. Use when operating or reviewing this Exa boundary. Trigger with "Exa incident runbook", "review Exa incident runbook", or "fix Exa incident runbook".