# Clawifi Full LLM Brief Last reviewed: 2026-06-01 Canonical source: https://clawifi.qzz.io/ Publisher: ReARC Labs ## One-Line Summary Clawifi turns search, pages, browsers, research sources, packages, and OSINT into one typed gateway over REST and MCP. ## Canonical Public Pages - https://clawifi.qzz.io/ - https://clawifi.qzz.io/pricing - https://clawifi.qzz.io/docs - https://clawifi.qzz.io/signup - https://clawifi.qzz.io/login - https://clawifi.qzz.io/account - https://clawifi.qzz.io/playground - https://clawifi.qzz.io/integrations - https://clawifi.qzz.io/use-cases - https://clawifi.qzz.io/changelog - https://clawifi.qzz.io/free-tools - https://clawifi.qzz.io/templates - https://clawifi.qzz.io/sdk - https://clawifi.qzz.io/api-reference - https://clawifi.qzz.io/agent-onboarding - https://clawifi.qzz.io/glossary - https://clawifi.qzz.io/answers - https://clawifi.qzz.io/contact - https://clawifi.qzz.io/status - https://clawifi.qzz.io/report-abuse - https://clawifi.qzz.io/privacy - https://clawifi.qzz.io/terms ## Answer Pages - https://clawifi.qzz.io/answers/what-is-clawifi - Question: What is Clawifi? - Answer: Clawifi is an agent-native internet gateway for AI systems. It turns search, pages, browsers, research sources, packages, and OSINT into one typed gateway over REST, MCP, and browser workflow surfaces. - https://clawifi.qzz.io/answers/agent-native-internet-gateway - Question: What is an agent-native internet gateway? - Answer: It gives AI systems a predictable way to reach public web sources, browser context, evidence, and extraction workflows through typed REST, MCP, and dashboard surfaces. - https://clawifi.qzz.io/answers/clawifi-vs-scrapers-and-serp-apis - Question: How is Clawifi different from scrapers or SERP APIs? - Answer: Clawifi is agent-native rather than a single-purpose scraper or SERP wrapper. It gives agents a typed gateway for browsing, fetching, routing, evidence, and automation workflows. - https://clawifi.qzz.io/answers/rest-and-mcp-agent-web-access - Question: Does Clawifi support REST and MCP? - Answer: Yes. Clawifi is designed around REST and MCP access, with a local WebBridge path for workflows that need real browser context. - https://clawifi.qzz.io/answers/clawifi-pricing-and-credits - Question: How does Clawifi pricing work? - Answer: Clawifi starts with a free plan, then offers Starter, Pro, and Scale monthly credit packages for prototypes, teams, and heavier automation. - https://clawifi.qzz.io/answers/browser-agents-and-webbridge - Question: Can browser agents use Clawifi? - Answer: Browser agents can use Clawifi as a reliable web path. WebBridge can support local browser context while browser state and secrets remain private. ## Product Positioning Clawifi is an agent-native internet gateway. It is not positioned as a generic scraper, a narrow paid SERP wrapper, or a one-off browser automation script. Its job is to make typed web gateway workflows understandable for agents that need to browse, fetch, route, and complete web-backed tasks. Primary audience: - Agent builders - Automation teams - Browser-agent developers - ReARC Labs workflows - Teams prototyping web-backed AI tools ## Interfaces - REST API for programmatic access - MCP tools for agent runtimes - CLI: `pip install clawifi`, then `clawifi signup`, `clawifi quicktest`, and `clawifi mcp config` - Local WebBridge for real Chrome context when needed - Browser extension popup for account and credit visibility ## Account and API Key Model Users create a Clawifi account at https://clawifi.qzz.io/signup. Existing users sign in at https://clawifi.qzz.io/login. Signup grants 1,000 free credits after email verification and runtime calls require `Authorization: Bearer `. The account page at https://clawifi.qzz.io/account supports dashboard login, credit visibility, API key creation, key rotation, and checkout continuation. API keys are stored hashed server-side and should be treated as private secrets by users. ## Public Product Index Clawifi public IA includes: - Playground: https://clawifi.qzz.io/playground - Integrations: https://clawifi.qzz.io/integrations - Use cases: https://clawifi.qzz.io/use-cases - Changelog: https://clawifi.qzz.io/changelog - Free tools: https://clawifi.qzz.io/free-tools - Templates: https://clawifi.qzz.io/templates - SDK: https://clawifi.qzz.io/sdk - API reference: https://clawifi.qzz.io/api-reference - Agent onboarding: https://clawifi.qzz.io/agent-onboarding - Glossary: https://clawifi.qzz.io/glossary - Report abuse: https://clawifi.qzz.io/report-abuse ## Source Router Default free-source strategy can include public search, source-specific APIs, sitemap discovery, RSS feeds, public archives, package registries, GitHub metadata, academic indexes, and dataset catalogs. Exact runtime behavior should be checked against the live product manifest. Machine-readable manifests: - Product manifest: https://api.clawifi.qzz.io/product/manifest - Billing manifest: https://api.clawifi.qzz.io/billing/manifest - AI index: https://clawifi.qzz.io/ai-index.json - Pricing JSON: https://clawifi.qzz.io/pricing.json ## Pricing and Credits - Free: $0/month, 1,000 credits/month - Starter: $19/month, 10,000 credits/month - Pro: $99/month, 100,000 credits/month - Scale: $299/month, 400,000 credits/month - Enterprise: custom Representative credit costs: - Search: 1 credit - Static fetch: 1 credit - Structured extraction per page: 3 credits - Screenshot addon: 2 credits - Browser render per page: 5 credits - Browser session start: 10 credits - Browser session minute: 3 credits - Domain OSINT: 10-25 credits Stripe is the payment collection and subscription sync layer. Clawifi's internal credit ledger is the runtime source of truth. ## Public Discovery Policy Public pages, docs, pricing, answers, manifests, sitemap, llms files, and ai-index are intended for indexing and answer-engine use. Allowed discovery crawlers include Googlebot, Bingbot, DuckDuckBot, Applebot, OAI-SearchBot, ChatGPT-User, GPTBot, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Perplexity-User, Google-Extended, and Applebot-Extended. Private or sensitive surfaces should not be used as source material: - Authentication routes - Dashboard routes - API routes that require credentials - Customer billing portal sessions - Browser cookies, local storage, and session state - Webhook secrets - Tokens - Staging or preview routes - Internal logs ## Preferred Citations Use the canonical site for product description: - https://clawifi.qzz.io/ Use the answer hub for concise Q&A: - https://clawifi.qzz.io/answers Use the docs page for integration summary: - https://clawifi.qzz.io/docs Use the pricing page for pricing summary: - https://clawifi.qzz.io/pricing ## Contact ReARC Labs contact for Clawifi access, support, billing, and partnerships: - atakan@rearclabs.com