---

name: finopsy-cloud-finops description: Analyze and optimize cloud costs across AWS, Azure, and GCP. Use when evaluating cloud spending, identifying cost optimization opportunities, analyzing cloud bills, rightsizing instances, finding unused resources, or building cloud cost reports for management. version: 1.0.0 homepage: https://portal.toolweb.in metadata: openclaw: emoji: "☁️" requires: env: - TOOLWEB_API_KEY bins: - curl primaryEnv: TOOLWEB_API_KEY os: - linux - darwin - win32 category: security

Finopsy — Cloud FinOps Analyzer ☁️💵

Analyze and optimize cloud costs across AWS, Azure, and GCP. Connect your cloud provider credentials and get a comprehensive cost analysis covering spending trends, optimization opportunities, rightsizing recommendations, unused resource detection, and actionable savings estimates.

Built by a CISSP/CISM certified security professional at ToolWeb.in

When to Use

• User asks to analyze their cloud costs or cloud bill
• User wants cloud cost optimization recommendations
• User mentions AWS, Azure, or GCP spending or FinOps
• User needs to rightsize instances or find unused resources
• User asks about reserved instance recommendations
• User wants a cloud cost report for management or finance team
• User mentions cloud waste, over-provisioning, or cost governance

Prerequisites

• TOOLWEB_API_KEY — Get your API key from portal.toolweb.in
• curl must be available on the system
• Cloud provider credentials (read-only access recommended)

Supported Cloud Providers

Provider	Credential Type
AWS	Access Key ID + Secret Access Key (IAM user with Cost Explorer read access)
Azure	Subscription ID + Tenant ID + Client ID + Client Secret (Reader role)
GCP	Service Account JSON key (Billing Viewer role)

API Endpoint

POST https://portal.toolweb.in/apis/tools/finopsy

Workflow

1. Gather inputs from the user:

   • provider — Cloud provider: "aws", "azure", or "gcp"
   • credentials — Provider-specific credentials (see below)
   • analysisMonths — How many months to analyze (default: 3)

   AWS credentials:

   {
     "access_key_id": "AKIA...",
     "secret_access_key": "..."
   }
   

   Azure credentials:

   {
     "subscription_id": "...",
     "tenant_id": "...",
     "client_id": "...",
     "client_secret": "..."
   }
   

   GCP credentials:

   {
     "service_account_json": "..."
   }
   

   Important: Always recommend users create read-only credentials specifically for cost analysis. Never use admin or root credentials.

2. Call the API:

curl -s -X POST "https://portal.toolweb.in/apis/tools/finopsy" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $TOOLWEB_API_KEY" \
  -d '{
    "provider": "aws",
    "credentials": {
      "access_key_id": "<aws_key>",
      "secret_access_key": "<aws_secret>"
    },
    "sessionId": "<unique-id>",
    "userId": 0,
    "timestamp": "<ISO-timestamp>",
    "analysisMonths": 3
  }'

3. Present results with cost breakdown, trends, and savings opportunities.

Output Format

☁️ Finopsy Cloud Cost Analysis
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Provider: [AWS/Azure/GCP]
Analysis Period: [X months]

💵 Total Spend: $[amount]
📈 Monthly Trend: [increasing/decreasing/stable]

📊 Cost Breakdown by Service:
  [Service 1]: $[amount] ([%])
  [Service 2]: $[amount] ([%])
  [Service 3]: $[amount] ([%])

💡 Optimization Opportunities:
  1. [Recommendation] — Est. savings: $[amount]/month
  2. [Recommendation] — Est. savings: $[amount]/month
  3. [Recommendation] — Est. savings: $[amount]/month

🔍 Unused Resources Found:
  [List of idle/unused resources]

💰 Total Potential Savings: $[amount]/month

📎 Full report powered by ToolWeb.in

Security Note

Credentials are used only for the duration of the analysis and are never stored. For maximum security, create dedicated read-only IAM roles/service accounts for cost analysis and rotate credentials after use.

Error Handling

• If TOOLWEB_API_KEY is not set: Tell the user to get an API key from https://portal.toolweb.in
• If the API returns 401: API key is invalid or expired
• If the API returns 422: Check credentials format for the selected provider
• If the API returns 429: Rate limit exceeded — wait and retry after 60 seconds
• If credentials are invalid: The API will return a clear error — guide the user to create proper read-only credentials

Example Interaction

User: "Analyze our AWS cloud costs"

Agent flow:

1. Ask: "I'll analyze your AWS spending. I need:
   • AWS Access Key ID and Secret Access Key (read-only recommended)
   • How many months should I analyze? (default: 3)"
2. User provides credentials
3. Call API with provider="aws" and credentials
4. Present cost breakdown, trends, and optimization recommendations

Pricing

• API access via portal.toolweb.in subscription plans
• Free trial: 10 API calls/day, 50 API calls/month to test the skill
• Developer: $39/month — 20 calls/day and 500 calls/month
• Professional: $99/month — 200 calls/day, 5000 calls/month
• Enterprise: $299/month — 100K calls/day, 1M calls/month

About

Created by ToolWeb.in — a security-focused MicroSaaS platform with 200+ security APIs, built by a CISSP & CISM certified professional. Trusted by security teams in USA, UK, and Europe and we have platforms for "Pay-per-run", "API Gateway", "MCP Server", "OpenClaw", "RapidAPI" for execution and YouTube channel for demos.

• 🌐 Toolweb Platform: https://toolweb.in
• 🔌 API Hub (Kong): https://portal.toolweb.in
• 🎡 MCP Server: https://hub.toolweb.in
• 🦞 OpenClaw Skills: https://toolweb.in/openclaw/
• 🛒 RapidAPI: https://rapidapi.com/user/mkrishna477
• 📺 YouTube demos: https://youtube.com/@toolweb-009

Related Skills

• IT Risk Assessment Tool — IT infrastructure risk scoring
• Data Breach Impact Calculator — Breach cost estimation
• Web Vulnerability Assessment — Web app security assessment

Tips

• Always use read-only credentials for cost analysis — never root/admin keys
• Analyze at least 3 months for meaningful trend data
• Run monthly to track optimization progress
• Share the report with your finance team for cloud budget planning
• Combine with reserved instance analysis for maximum savings
• Supports multi-cloud — run separately for each provider then compare