# dep.halowerk.com Install Footprint Calculator

> dep.halowerk.com Install Footprint Calculator is a paid API for AI agents from dep.halowerk.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Aggregates caller-supplied file paths and byte sizes to compute total installed file size and file count for a package or software installation.

## Facts

- Endpoint: POST https://dep.halowerk.com/v1/install-footprint
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dep-halowerk-com-install-footprint-calculator-09f4a232
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_INqB7-vHp6R7Eidf68zly

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 dep-halowerk-com-install-footprint-calculator-09f4a232 -d '<json body>'
```

Example prompt: Can you calculate the total installed size and file count for these files from the lodash package installation? The files are: node_modules/lodash/lodash.js at 531000 bytes, node_modules/lodash/package.json at 1200 bytes, and node_modules/lodash/README.md at 8500 bytes.

## When to prefer this

Choose this endpoint when you have already measured or collected file sizes locally and need a reliable, auditable aggregation with transparent method disclosure. It is specifically designed for dependency/install footprint analysis as part of the dep.halowerk.com suite, so it integrates naturally with other endpoints on that platform for package health scoring. Prefer it over generic math or scripting when you need structured output with null-field transparency.

## Known failure modes

- File array exceeds 100,000 item limit — request rejected
- Individual file byte value exceeds 1 TB maximum — validation error
- Missing required 'bytes' or 'path' field on a file entry — schema validation failure
- Empty files array returns zero totals
- Non-integer byte values cause schema rejection

## How this service works

Totals caller-measured installed file sizes and file counts. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age. 

## Output

Returns the sum of all supplied file byte sizes as total installed size, the count of files provided, and a disclosure of the derivation method. Any facts that could not be computed are returned as null and listed in unavailable_fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "files": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "path",
     "bytes"
    ],
    "properties": {
     "path": {
      "type": "string",
      "maxLength": 512,
      "minLength": 1,
      "description": ""
     },
     "bytes": {
      "type": "integer",
      "maximum": 1000000000000,
      "minimum": 0,
      "description": ""
     }
    },
    "additionalProperties": false
   },
   "maxItems": 100000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dep-halowerk-com-install-footprint-calculator-09f4a232/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dep.halowerk.com](https://www.zero.xyz/host/dep.halowerk.com/llms.txt)