# Clawifi Full LLM Brief Last reviewed: 2026-06-01 Canonical source: https://clawifi.dev/ 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.dev/ - https://clawifi.dev/pricing - https://clawifi.dev/docs - https://clawifi.dev/signup - https://clawifi.dev/login - https://clawifi.dev/account - https://clawifi.dev/playground - https://clawifi.dev/integrations - https://clawifi.dev/use-cases - https://clawifi.dev/changelog - https://clawifi.dev/free-tools - https://clawifi.dev/templates - https://clawifi.dev/sdk - https://clawifi.dev/api-reference - https://clawifi.dev/agent-onboarding - https://clawifi.dev/glossary - https://clawifi.dev/answers - https://clawifi.dev/contact - https://clawifi.dev/status - https://clawifi.dev/report-abuse - https://clawifi.dev/privacy - https://clawifi.dev/terms ## Answer Pages - https://clawifi.dev/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.dev/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.dev/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.dev/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. - Question: Is there a remote MCP server? - Answer: Yes, since 1.6.0: https://api.clawifi.dev/mcp over streamable HTTP, with the API key as `Authorization: Bearer` (or `X-Clawifi-Api-Key`). Each tool call is billed like the REST route it runs. Without a key, search_free, fetch_url, scrape_url and map_site work as a trial (12 calls a minute, 50 a day per address). OAuth is not offered. - Question: Can a team share Clawifi? - Answer: Yes, through organizations: owners and admins invite people by email as admins or members. Calls in an organization are paid from its owner's credits, on the owner's plan. Removing a member revokes the keys they created there. - https://clawifi.dev/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.dev/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_API_KEY=your_key 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.dev/signup. Existing users sign in at https://clawifi.dev/login. Signup grants 1,000 free credits after email verification and runtime calls require `Authorization: Bearer `. The account page at https://clawifi.dev/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.dev/playground - Integrations: https://clawifi.dev/integrations - Use cases: https://clawifi.dev/use-cases - Changelog: https://clawifi.dev/changelog - Free tools: https://clawifi.dev/free-tools - Templates: https://clawifi.dev/templates - SDK: https://clawifi.dev/sdk - API reference: https://clawifi.dev/api-reference - Agent onboarding: https://clawifi.dev/agent-onboarding - Glossary: https://clawifi.dev/glossary - Report abuse: https://clawifi.dev/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.dev/product/manifest - Billing manifest: https://api.clawifi.dev/billing/manifest - AI index: https://clawifi.dev/ai-index.json - Pricing JSON: https://clawifi.dev/pricing.json - Docs as Markdown: https://clawifi.dev/docs.md - Changelog as Markdown: https://clawifi.dev/changelog.md ## Pricing and Credits - Free: $0/month, 1,000 credits/month - Starter: $19/month, 10,000 credits/month - Pro: $99/month, 125,000 credits/month - Scale: $299/month, 500,000 credits/month - Enterprise: custom Representative credit costs (the live table is in the billing manifest): - Search, static fetch, scrape, article extract: 1 credit - Package, dataset, code, archive and academic lookups, a single OSINT lookup, social reads: 1 credit - Browser render, or a fetch that escalates to the browser: 3 credits - PDF: 2 credits per started 50 pages - Map: 1 credit per started 10 URLs returned - Crawl: 1 credit per page, +2 per page that needed JS rendering - Monitor check: 1 credit, 3 with the browser - OSINT recon bundle (domain, email, username): 5 credits - Research: 30 to 300 credits, by sources searched and pages read - Research plan: 5 credits - Hosted browser render (Pro and Scale; 500 and 2,500 minutes a month): 6 credits per started browser-minute, at least 6. Renders JavaScript-heavy pages in a hosted browser. It does not bypass bot protection or CAPTCHAs. - Passages (query/top_k), cache hits and failed calls: 0 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.dev/ Use the answer hub for concise Q&A: - https://clawifi.dev/answers Use the docs page for integration summary: - https://clawifi.dev/docs Use the pricing page for pricing summary: - https://clawifi.dev/pricing ## Contact ReARC Labs contact for Clawifi access, support, billing, and partnerships: - clawifisupport@rearclabs.com