# Cache Key Explosion Auditor

> Cache Key Explosion Auditor is a paid API for AI agents from mcp-factory.bowling-anthony.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Analyzes HTTP request log samples to detect cache key explosion patterns and propose normalized, deduplicated cache keys

## Facts

- Endpoint: POST https://mcp-factory.bowling-anthony.workers.dev/cache-key-explosion-auditor/analyze
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cache-key-explosion-auditor-37f8242b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cs5IKzmlKMg41YY5AP5MB

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 cache-key-explosion-auditor-37f8242b -d '<json body>'
```

Example prompt: Can you audit these HTTP request log samples for cache key explosion — I suspect utm_source and param ordering are fragmenting my cache — and propose normalized cache keys that consolidate the duplicates?

## When to prefer this

Use this endpoint when you need to programmatically audit HTTP request logs for cache key explosion — especially when tracking parameters, query string ordering, or URL fragments are suspected of fragmenting your CDN or reverse proxy cache. It is purpose-built for detecting and proposing fixes to cache key bloat, unlike general-purpose log analytics tools that lack cache-key-specific normalization logic.

## Known failure modes

- Invalid or malformed request sample input returns an error
- Empty sample set returns empty groups with zero counts
- Conflicting normalization rules may produce unexpected key collapses
- Payment failure via x402 prevents call execution
- Large sample sets may hit timeout or size limits on the worker

## How this service works

Customer-input analysis tools with per-call x402 v2 USDC payments on Base. Discovery and examples are free.

## Output

Returns a JSON object with normalization rules applied (e.g. dropped query params, sorted params, fragment handling), grouped request clusters showing which original keys map to each proposed key, conflict flags where distinct content might share a key, and a summary with counts of requests, original keys, proposed keys, variants removed, and conflict groups detected.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "rules": {
   "drop_fragment": false,
   "drop_query_params": [
    "utm_source"
   ],
   "sort_query_params": true
  },
  "scope": "supplied_samples_only",
  "groups": [
   {
    "assessment": "conflict",
    "proposed_key": "GET https://shop.example.com/p/1?id=1",
    "sampled_hits": 820,
    "original_keys": [
     "GET https://shop.example.com/p/1?utm_source=x&id=1",
     "GET https://shop.example.com/p/1?id=1&utm_source=y",
     "GET https://shop.example.com/p/1?id=1&utm_source=z"
    ],
    "sample_indices": [
     0,
     1,
     2
    ],
    "representation_ids": [
     "r1",
     "r2"
    ]
   }
  ],
  "summary": {
   "requests": 3,
   "sampled_hits": 820,
   "original_keys": 3,
   "proposed_keys": 1,
   "unproven_groups": 0,
   "variants_removed": 2,
   "observed_conflict_groups": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cache-key-explosion-auditor-37f8242b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp-factory.bowling-anthony.workers.dev](https://www.zero.xyz/host/mcp-factory.bowling-anthony.workers.dev/llms.txt)