Firecrawl API keys

• Provider documentation parseApi.ts strips fc- and re-inserts the 8-4-4-4-12 dashes (last changed 2026-05-15, re-checked 2026-09-28); api_keys.key is uuid().defaultRandom() · observed 2026-09-28 · the docs and SDK document the fc- prefix; provider server code (ruling R1) makes the body a dashless lowercase random UUIDv4 (32 hex, version nibble 4, variant 8/9/a/b), 35 in all
• Reference 1
• Reference 2
• Reference 3
• Reference 4
• Reference 5
• Reference 6
• Reference 7
• Reference 8
• Reference 9
• Reference 10
• Reference 11
• Reference 12

Arrival evidence (#434, product redact-secret#908; #860 handoff firecrawl.md, READY). A Firecrawl key spends the team's crawl and scrape credits and is common in agent web tools and MCP servers. The prefix is documented and checked by the SDK and MCP server; the body is a dashless Postgres random UUIDv4 by the server normalizer, schema default and validator (R1), so the version and variant nibbles are enforced, rejecting 63 of 64 arbitrary 32-hex runs (an fc- + MD5, say) at no cost for issued keys. Excluded: legacy bare dashed UUIDs (not attributable), fc- + a dashed UUID (not an issued form), another UUID version or variant, uppercase hex, fco_ and fcmcp_. Neither pinned peer has a Firecrawl rule. Graduated to a registry detector at the 1127bf9 re-pin (redact-secret PR #938).