<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Sivanandam S — Blog</title>
    <link>https://www.sivanandam.in/blog/</link>
    <description>Sivanandam S is an ISTQB certified test analyst with 15+ years testing web, mobile, OTT, chatbot and smart wearable applications. Notes on test automation, AI security and quality engineering.</description>
    <language>en-in</language>
    <managingEditor>siva@hey.com (Sivanandam S)</managingEditor>
    <lastBuildDate>Fri, 04 Sep 2026 03:01:44 GMT</lastBuildDate>
    <atom:link href="https://www.sivanandam.in/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Claude Pro vs Anthropic API &amp; OpenClaw Usage Cost</title>
      <link>https://www.sivanandam.in/blog/claude-pro-vs-anthropic-api-cost/</link>
      <guid isPermaLink="true">https://www.sivanandam.in/blog/claude-pro-vs-anthropic-api-cost/</guid>
      <pubDate>Wed, 18 Feb 2026 09:00:00 GMT</pubDate>
      <category>AI Tooling</category>
      <description>Claude Pro and the Anthropic API are separate products: a Claude Pro subscription does not include an API key, API credits, or programmatic access. To run OpenClaw you need your own key from console.anthropic.com with billing enabled, which typically costs $20-$60 per month for light personal use and $75-$250 for daily automation work.</description>
      <content:encoded><![CDATA[<div class="section"><h2>Does Claude Pro include an Anthropic API key?</h2><p><strong>No — it does not.</strong></p><p>Claude Pro (the web subscription plan) gives you:</p><ul><li>Access to Claude models inside the Claude web app</li><li>Higher usage limits than the free tier</li><li>Priority access to newer models</li></ul><p>Claude Pro <strong>does NOT include:</strong></p><ul><li>An Anthropic API key</li><li>API credits</li><li>Programmatic access</li></ul><div class="box">OpenClaw requires an Anthropic API key from the developer console (console.anthropic.com). Claude Pro ≠ API access.</div><h3>Why are Claude Pro and the Anthropic API separate products?</h3><p>This separation is standard across AI providers:</p><ul><li>ChatGPT Plus ≠ OpenAI API credits</li><li>Claude Pro ≠ Anthropic API credits</li></ul><p>The web subscription is a consumer SaaS product. The API is a developer infrastructure product with usage-based billing.</p><h3>Why does Anthropic billing show “Buy Credits”?</h3><p>That refers to API credits. It means you haven’t added billing funds for programmatic usage.</p><table><caption>Claude Pro subscription compared with Anthropic API access</caption><thead><tr><th scope="col">Product</th><th scope="col">Includes API key?</th><th scope="col">Used for</th></tr></thead><tbody><tr><th scope="row">Claude Pro</th><td>❌ No</td><td>Web chat only</td></tr><tr><th scope="row">Anthropic API</th><td>✅ Yes (after billing)</td><td>OpenClaw, scripts, automation</td></tr></tbody></table><p><strong>To use OpenClaw:</strong></p><ol><li>Create an API key at console.anthropic.com</li><li>Add billing / buy credits</li><li>Export your key in Ubuntu:</li></ol><p><code>export ANTHROPIC_API_KEY="your_key_here"</code></p></div><div class="section"><h2>How much does OpenClaw cost per month?</h2><p>Cost depends on:</p><ul><li>Model used (Sonnet vs higher-tier)</li><li>Project size</li><li>Daily usage frequency</li><li>Iteration loops</li><li>Context size sent repeatedly</li></ul><h3>Light usage: personal development</h3><ul><li>20–40 prompts per day</li><li>Small repository</li><li>Short edits</li></ul><p><strong>Estimated Monthly Cost:</strong> $20 – $60</p><h3>Moderate usage: daily automation work</h3><ul><li>50–100 prompts per day</li><li>Medium-sized repo</li><li>Frequent refactoring + debugging</li></ul><p><strong>Estimated Monthly Cost:</strong> $75 – $250</p><h3>Heavy usage: enterprise and large codebases</h3><ul><li>Large repository context</li><li>Long reasoning loops</li><li>Continuous generation</li></ul><p><strong>Estimated Monthly Cost:</strong> $300 – $1,200+</p><div class="box">Most automation engineers using Sonnet-class models for Playwright/POM development fall in the <span class="highlight">$50 – $150 per month</span> range.</div><h3>How can you reduce OpenClaw costs?</h3><ul><li>Use Sonnet instead of higher-tier models unless necessary</li><li>Keep prompts precise</li><li>Avoid sending entire repository repeatedly</li><li>Clear conversation context when switching tasks</li><li>Avoid unnecessary regeneration loops</li></ul></div>]]></content:encoded>
    </item>
    <item>
      <title>Using Strix Open‑Source AI Hacker for Automated Penetration Testing (Windows)</title>
      <link>https://www.sivanandam.in/blog/using-strix-ai-hacker-automated-pentesting-windows/</link>
      <guid isPermaLink="true">https://www.sivanandam.in/blog/using-strix-ai-hacker-automated-pentesting-windows/</guid>
      <pubDate>Tue, 13 Jan 2026 09:00:00 GMT</pubDate>
      <category>Security Testing</category>
      <description>Strix is an open-source AI hacker that automates penetration testing with large language models. On Windows, install it with pipx install &quot;strix-agent[vertex]&quot;, enable Vertex AI on a billed Google Cloud project, set the STRIX_LLM, VERTEXAI_PROJECT and VERTEXAI_LOCATION environment variables, authenticate with gcloud auth application-default login instead of an API key, then run it against a target you are authorized to test.</description>
      <content:encoded><![CDATA[<h2>Overview</h2><ul><li><strong>OS:</strong> Windows</li><li><strong>Tool:</strong> Strix (open‑source AI hacker)</li><li><strong>LLM Provider:</strong> Google Vertex AI</li><li><strong>Model:</strong> <code>vertex_ai/gemini-2.5-pro</code></li><li><strong>Authentication:</strong> Google Cloud Application Default Credentials</li><li><strong>Target Application:</strong> Dummy web application</li></ul><h2>Prerequisites</h2><p>Ensure the following are installed and running:</p><ul><li>Python</li><li>Docker</li><li>Google Cloud SDK</li><li>LLM Provider Access</li></ul><h3>Authentication Notes</h3><ul><li>No API key required</li><li>Authentication handled via Google Cloud Application Default Credentials</li></ul><h2>Step 1: Install Strix</h2><p>Since this setup uses Gemini models via Vertex AI, install Strix with Vertex support:</p><pre><code>pipx install "strix-agent[vertex]"</code></pre><p>If you plan to use OpenAI or Claude instead, install Strix without extras:</p><pre><code>pipx install strix-agent</code></pre><h2>Step 2: Create or Select a Google Cloud Project</h2><p>Vertex AI requires a Google Cloud project.</p><h3>Option A: Use an Existing Project</h3><p>If you already have projects in GCP:</p><pre><code>gcloud projects list</code></pre><p>Select one from the list.</p><h3>Option B: Create a New Project (Recommended)</h3><pre><code>gcloud projects create my-strix-project
gcloud config set project my-strix-project</code></pre><h2>Step 3: Enable Vertex AI</h2><p>Enable the Vertex AI API for the selected project:</p><pre><code>gcloud services enable aiplatform.googleapis.com</code></pre><p>Alternatively, enable it through the Google Cloud Console:</p><pre><code>https://console.developers.google.com/apis/api/aiplatform.googleapis.com/overview?project=&lt;your_project&gt;</code></pre><h3>Enable Billing</h3><p>Vertex AI requires billing to be enabled for the project:</p><pre><code>https://console.developers.google.com/billing/enable?project=&lt;yourproject&gt;</code></pre><h2>Step 4: Configure Environment Variables</h2><p>Set the required environment variables in Command Prompt (<code>cmd.exe</code>):</p><pre><code>set STRIX_LLM=vertex_ai/gemini-2.5-pro
set VERTEXAI_PROJECT=my-strix-project
set VERTEXAI_LOCATION=us-central1</code></pre><h2>Step 5: Authenticate with Google Cloud</h2><p>Authenticate using Application Default Credentials:</p><pre><code>gcloud auth application-default login</code></pre><p>This allows Strix to securely access Vertex AI without storing API keys.</p><h2>How do you run Strix against a target application?</h2><h3>Run with Inline Instructions</h3><pre><code>strix --target https://dummy-app.example.com --instruction "perform authenticated testing using credentials: username:password"</code></pre><h3>Run with an Instruction File</h3><pre><code>strix --target https://dummy-app.example.com --instruction-file ./instructions_pentest.md</code></pre><h2>What does a Strix instruction file look like?</h2><p>Below is a sample <code>instructions_pentest.md</code> file:</p><pre><code># Penetration Test Instructions

## Credentials
- Admin: admin_user / StrongPassword@123

## Focus Areas
1. Injection Attacks – SQL, NoSQL, command injection
2. Server-Side Issues – SSRF, XXE, deserialization flaws
3. Infrastructure – Misconfigurations, exposed services
4. Client-Side – XSS, prototype pollution, DOM vulnerabilities

## In Scope
/app-audit
/admin-console
/vendor-dashboard

## Out of Scope
- Third-party integrations</code></pre><h2>Why use Gemini 2.5 Pro for security scanning?</h2><ul><li>Latest stable Pro‑grade Gemini model</li><li>Deep reasoning and long‑context understanding</li><li>Strong performance in code analysis and vulnerability discovery</li><li>Ideal for security scanning where quality matters more than speed</li></ul><h2>Final Thoughts</h2><p>Using Strix with Vertex AI Gemini 2.5 Pro provides a powerful, automated approach to penetration testing. By relying on Google Cloud’s authentication and managed AI infrastructure, you avoid API key management while benefiting from high‑quality security analysis.</p><p>Always ensure you have explicit authorization before running security scans against any application.</p><h3>Disclaimer</h3><p>This content is for educational and authorized security testing purposes only.</p>]]></content:encoded>
    </item>
    <item>
      <title>Welcome to My New Digital Home</title>
      <link>https://www.sivanandam.in/blog/welcome-to-my-new-digital-home/</link>
      <guid isPermaLink="true">https://www.sivanandam.in/blog/welcome-to-my-new-digital-home/</guid>
      <pubDate>Mon, 12 Jan 2026 09:00:00 GMT</pubDate>
      <category>Notes</category>
      <description>I&#39;ve decided to revamp my personal website to better reflect my journey in the digital realm. Here&#39;s a look at the new design philosophy.</description>
      <content:encoded><![CDATA[<p>Welcome! After years of using standard templates, I decided it was time for a refresh. Use this space to share your thoughts, updates, and more.</p><p>This new site is built with performance and aesthetics in mind, using a custom glassmorphism design system.</p>]]></content:encoded>
    </item>
    <item>
      <title>The Future of Test Automation</title>
      <link>https://www.sivanandam.in/blog/future-of-test-automation-ai-agents/</link>
      <guid isPermaLink="true">https://www.sivanandam.in/blog/future-of-test-automation-ai-agents/</guid>
      <pubDate>Sun, 28 Dec 2025 09:00:00 GMT</pubDate>
      <category>Test Automation</category>
      <description>Exploring how AI agents and LLMs are revolutionizing the way we approach QA and test automation.</description>
      <content:encoded><![CDATA[<p>Test automation is evolving rapidly. With the advent of advanced AI agents, we are moving from script-based testing to intent-based testing.</p><p>In this post, I explore how tools like Selenium and Playwright are being augmented by AI to self-heal and generate tests automatically.</p>]]></content:encoded>
    </item>
    <item>
      <title>Exploring Smart Wearables QA</title>
      <link>https://www.sivanandam.in/blog/exploring-smart-wearables-qa/</link>
      <guid isPermaLink="true">https://www.sivanandam.in/blog/exploring-smart-wearables-qa/</guid>
      <pubDate>Sat, 15 Nov 2025 09:00:00 GMT</pubDate>
      <category>Quality Engineering</category>
      <description>Testing wearables presents unique challenges compared to traditional mobile apps. From battery usage to sensor data validation.</description>
      <content:encoded><![CDATA[<p>Smart wearables are becoming ubiquitous. Testing them requires a different mindset. You aren't just testing a screen; you're testing an ecosystem.</p><ul><li>Battery drain analysis</li><li>Bluetooth connectivity stability</li><li>Sensor accuracy validation</li></ul>]]></content:encoded>
    </item>
  </channel>
</rss>
