# BRAINIAC Cloud FinOps — Idle Resource Detector

> BRAINIAC Cloud FinOps — Idle Resource Detector is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-17).

Analyzes a list of cloud resources by CPU usage and observation period to identify which ones are idle and eligible for cost savings.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/cloud-finops/idle-resource-detect?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-cloud-finops-idle-resource-detector-88e208af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UGG-yxSnhfmlevffvHCEO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-cloud-finops-idle-resource-detector-88e208af -d '<json body>'
```

Example prompt: Check these 3 cloud resources for idleness — i-abc123 (compute, 14 days observed, 2% CPU, $40/month), i-def456 (compute, 7 days observed, 12% CPU, $20/month), and i-ghi789 (compute, 20 days observed, null CPU, $60/month) — using a CPU threshold of 5% and a minimum of 14 days observed.

## When to prefer this

Use this endpoint when you have your own resource utilization data (CPU percent, days observed, optional cost) and want a structured idle-detection analysis without connecting a live cloud account. It is ideal for agent workflows that already export or collect utilization metrics and need a rules-based idle classification step. Prefer this over live-cloud FinOps tools when you do not want any infrastructure changes made and simply need a decision on which resources are idle candidates.

## Known failure modes

- Missing required fields (resourceId, resourceType, daysObserved) cause validation errors
- Supplying more than 500 resources exceeds the maxItems limit
- CPU data absent for a resource results in 'insufficient' status rather than 'idle', not an error
- Resources observed fewer days than minimumDays threshold will not be flagged idle regardless of CPU
- Payment failure via x402 returns HTTP 402 and no result

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with a top-level status, a list of resources each labeled as 'idle', 'active', or 'insufficient' (when CPU data is missing), structured findings explaining the idle detection rule applied, the timestamp of the check, and a limitations array clarifying that no cloud account was connected and no live infrastructure was changed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "resources": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "resourceId",
     "resourceType",
     "daysObserved"
    ],
    "properties": {
     "cost": {
      "type": "number",
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "currency": {
      "type": "string",
      "pattern": "^[A-Za-z]{3}$"
     },
     "cpuPercent": {
      "type": "number",
      "maximum": 100,
      "minimum": 0
     },
     "resourceId": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
     },
     "daysObserved": {
      "type": "integer",
      "maximum": 3660,
      "minimum": 0
     },
     "resourceType": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 500,
   "minItems": 1
  },
  "minimumDays": {
   "type": "integer",
   "maximum": 3660,
   "minimum": 1
  },
  "cpuThreshold": {
   "type": "number",
   "maximum": 100,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "idle_observed",
  "findings": [
   {
    "code": "idle_rule",
    "kind": "extracted",
    "detail": "Compute is idle only when daysObserved is at least 14 and cpuPercent is below the supplied threshold 5. Missing CPU is not treated as idle."
   }
  ],
  "checkedAt": "2026-11-02T19:00:00.000Z",
  "resources": [
   {
    "status": "idle",
    "currency": "USD",
    "cpuPercent": 2,
    "resourceId": "i-idle",
    "daysObserved": 14,
    "suppliedCost": 40
   },
   {
    "status": "insufficient",
    "currency": "USD",
    "cpuPercent": null,
    "resourceId": "i-unknown",
    "daysObserved": 14,
    "suppliedCost": 40
   }
  ],
  "limitations": [
   "No cloud account was connected and no infrastructure was changed.",
   "Costs and forecasts use only figures supplied in the request.",
   "Provider list prices are not added, and no saving is claimed without a supplied cost.",
   "The billing format is brainiac-billing-v1. Native provider exports are not accepted."
  ],
  "accountConnected": false,
  "infrastructureChanged": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-cloud-finops-idle-resource-detector-88e208af/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
