Clay Cost TuningSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: clay-cost-tuning description: 'Optimize Clay credit spending with provider key management, waterfall tuning, and budget controls. Use when analyzing Clay costs, reducing credit consumption, or implementing spending alerts and caps. Trigger with phrases like "clay cost", "clay billing", "reduce clay costs", "clay pricing", "clay expensive", "clay budget", "clay credits". ' allowed-tools: Read, Write, Edit, Grep version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - clay - api - monitoring - cost-optimization compatibility: Designed for Claude Code --- # Clay Cost Tuning ## Overview Reduce Clay data enrichment spending by connecting your own API keys (70-80% savings), optimizing waterfall depth, improving input data quality, and implementing budget controls. Clay's March 2026 pricing split credits into Data Credits and Actions, changing the optimization calculus. ## Prerequisites - Clay account with visibility into credit consumption - Understanding of which enrichment columns are in your tables - Access to Clay Settings > Plans & Billing ## Instructions ### Step 1: Connect Your Own Provider API Keys (Biggest Savings) This is the single most impactful cost reduction. Clay charges 0 Data Credits when you use your own API keys: | Provider | Clay-Managed Cost | Own Key Cost | Annual Savings (10K rows/mo) | |----------|-------------------|-------------|------------------------------| | Apollo | 2 credits/lookup | 0 credits | ~240K credits/year | | Clearbit | 2-5 credits | 0 credits | ~360K credits/year | | Hunter.io | 2 credits | 0 credits | ~240K credits/year | | Prospeo | 2 credits | 0 credits | ~240K credits/year | | People Data Labs | 3 credits | 0 credits | ~360K credits/year | | ZoomInfo | 5-13 credits | 0 credits | ~1M+ credits/year | **Setup:** Go to **Settings > Connections** in Clay, click **Add Connection**, and paste your provider API key. All enrichments using that provider will consume 0 Clay credits (1 Action is still consumed per enrichment). ### Step 2: Optimize Waterfall Enrichment Depth Each waterfall step costs credits (if using Clay-managed keys) and time: ```yaml # Expensive waterfall (5 providers, 10-15 credits/row): expensive: - apollo: 2 credits - hunter: 2 credits - prospeo: 2 credits - dropcontact: 3 credits - findymail: 3 credits total_max: 12 credits/row coverage: ~92% # Optimized waterfall (2 providers, 4 credits/row): optimized: - apollo: 2 credits # Highest coverage provider first - hunter: 2 credits # Strong backup total_max: 4 credits/row coverage: ~83% savings: "67% credit reduction, ~9% coverage loss" ``` **March 2026 change:** Failed lookups no longer cost Data Credits. This makes wider waterfalls less expensive than before, since you only pay when data is actually found. ### Step 3: Pre-Filter Input Data Credits wasted on unenrichable rows are the most common cost leak: ```typescript // src/clay/cost-filter.ts function estimateCreditCost(rows: any[], creditsPerRow: number): { filteredRows: any[]; estimatedCredits: number; savings: number; } { const personalDomains = new Set([ 'gmail.com', 'yahoo.com', 'hotmail.com', 'outlook.com', 'icloud.com', ]); const filtered = rows.filter(row => { if (!row.domain?.includes('.')) return false; if (personalDomains.has(row.domain)) return false; if (!row.first_name || !row.last_name) return false; return true; }); // Deduplicate const seen = new Set<string>(); const deduped = filtered.filter(row => { const key = `${row.domain}:${row.first_name}:${row.last_name}`.toLowerCase(); if (seen.has(key)) return false; seen.add(key); return true; }); return { filteredRows: deduped, estimatedCredits: deduped.length * creditsPerRow, savings: (rows.length - deduped.length) * creditsPerRow, }; } // Usage const { filteredRows, estimatedCredits, savings } = estimateCreditCost(rawLeads, 6); console.log(`Will process ${filteredRows.length} rows (${estimatedCredits} credits)`); console.log(`Saved ${savings} credits by pre-filtering`); ``` ### Step 4: Use Sampling Before Full Runs Test enrichment quality on a small sample before committing credits to the full list: ```typescript // src/clay/sampler.ts function sampleForTest(rows: any[], sampleSize = 100): { sample: any[]; remaining: any[]; estimatedTotalCredits: number; } { // Random sample for representative results const shuffled = [...rows].sort(() => Math.random() - 0.5); const sample = shuffled.slice(0, sampleSize); const remaining = shuffled.slice(sampleSize); return { sample, remaining, estimatedTotalCredits: rows.length * 6, // Estimate 6 credits/row average }; } // Workflow: // 1. Send sample (100 rows) to Clay test table // 2. Check hit rate after enrichment completes // 3. If hit rate > 60%, proceed with full list // 4. If hit rate < 40%, clean input data first ``` ### Step 5: Implement Credit Budget Alerts ```typescript // src/clay/budget-monitor.ts interface CreditBudget { monthlyLimit: number; // From your plan dailyThreshold: number; // Alert if exceeded perTableMax: number; // Cap per table } const PLAN_BUDGETS: Record<string, CreditBudget> = { launch: { monthlyLimit: 2_500, dailyThreshold: 125, perTableMax: 500 }, growth: { monthlyLimit: 6_000, dailyThreshold: 300, perTableMax: 1_500 }, enterprise: { monthlyLimit: 50_000, dailyThreshold: 2_500, perTableMax: 10_000 }, }; class BudgetMonitor { private dailyUsage = 0; private monthlyUsage = 0; private tableUsage = new Map<string, number>(); constructor(private budget: CreditBudget) {} recordUsage(tableId: string, credits: number) { this.dailyUsage += credits; this.monthlyUsage += credits; this.tableUsage.set(tableId, (this.tableUsage.get(tableId) || 0) + credits); // Check thresholds if (this.dailyUsage > this.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__clay-cost-tuning.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Clay Cost Tuning skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Clay Cost Tuning safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Clay Cost Tuning access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Clay Cost Tuning work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.