intercom-cost-tuning
Optimize Intercom API costs through caching, request reduction, and usage monitoring. Use when analyzing Intercom API usage, reducing unnecessary requests, or implementing usage tracking and budget awareness. Trigger with phrases like "intercom cost", "intercom billing", "reduce intercom requests", "intercom pricing", "intercom usage", "intercom budget".
What this skill does
# Intercom Cost Tuning
## Overview
Reduce Intercom API costs through smart caching, search optimization, webhook-driven architecture, and usage monitoring. Intercom pricing is primarily seat-based and feature-based, but API efficiency reduces infrastructure costs and avoids rate limits.
## Intercom Pricing Model
| Component | Pricing Basis | Cost Driver |
|-----------|--------------|-------------|
| Seats | Per agent/month | Number of teammates |
| Fin AI Agent | Per resolution | AI-handled conversations |
| Proactive Support | Per message sent | Outbound messages volume |
| Help Center | Included | N/A |
| API | Included (rate-limited) | Request volume determines infra cost |
**Key insight:** The API itself is free to use, but hitting rate limits (10K req/min) forces you to build queuing infrastructure. Reducing requests saves engineering time and infrastructure costs.
## Instructions
### Step 1: Audit Current API Usage
```typescript
// Instrument all API calls to track usage patterns
class IntercomUsageTracker {
private calls = new Map<string, { count: number; totalMs: number }>();
track(endpoint: string, durationMs: number): void {
const existing = this.calls.get(endpoint) || { count: 0, totalMs: 0 };
existing.count++;
existing.totalMs += durationMs;
this.calls.set(endpoint, existing);
}
report(): void {
console.log("\n=== Intercom API Usage Report ===");
const sorted = [...this.calls.entries()].sort((a, b) => b[1].count - a[1].count);
for (const [endpoint, stats] of sorted) {
console.log(
`${endpoint}: ${stats.count} calls, avg ${(stats.totalMs / stats.count).toFixed(0)}ms`
);
}
const total = sorted.reduce((sum, [, s]) => sum + s.count, 0);
console.log(`\nTotal: ${total} API calls`);
console.log(`Estimated rate: ${(total / 60).toFixed(0)} req/min (limit: 10,000)`);
}
}
```
### Step 2: Replace Polling with Webhooks
```typescript
// BAD: Polling for new conversations every 30 seconds
// Cost: ~2,880 requests/day for ONE check
setInterval(async () => {
const conversations = await client.conversations.list();
// Check for new conversations...
}, 30000);
// GOOD: Webhook-driven (0 requests, instant notification)
app.post("/webhooks/intercom", (req, res) => {
const notification = req.body;
if (notification.topic === "conversation.user.created") {
handleNewConversation(notification.data.item);
}
res.status(200).json({ received: true });
});
```
### Step 3: Cache Contact Lookups
```typescript
import { LRUCache } from "lru-cache";
const contactCache = new LRUCache<string, any>({
max: 10000,
ttl: 10 * 60 * 1000, // 10 min TTL
});
// Before: 1 API call per contact lookup
async function getContactName(contactId: string): Promise<string> {
const contact = await client.contacts.find({ contactId });
return contact.name;
}
// After: API call only on cache miss
async function getContactNameCached(contactId: string): Promise<string> {
let name = contactCache.get(contactId) as string | undefined;
if (!name) {
const contact = await client.contacts.find({ contactId });
name = contact.name;
contactCache.set(contactId, name);
}
return name;
}
// Invalidate cache via webhooks
function onContactUpdated(contactId: string): void {
contactCache.delete(contactId);
}
```
### Step 4: Use Search Instead of List + Filter
```typescript
// BAD: Fetch all contacts, filter client-side
// Cost: N pages * 1 request each
let startingAfter: string | undefined;
const matchingContacts = [];
do {
const page = await client.contacts.list({ perPage: 50, startingAfter });
matchingContacts.push(...page.data.filter(c => c.customAttributes?.plan === "pro"));
startingAfter = page.pages?.next?.startingAfter;
} while (startingAfter);
// GOOD: Server-side search (1 request for up to 150 results)
const proUsers = await client.contacts.search({
query: {
operator: "AND",
value: [
{ field: "role", operator: "=", value: "user" },
{ field: "custom_attributes.plan", operator: "=", value: "pro" },
],
},
pagination: { per_page: 150 },
});
```
### Step 5: Batch Conversation Lookups
```typescript
// BAD: N individual conversation lookups
for (const id of conversationIds) {
const convo = await client.conversations.find({ conversationId: id });
process(convo);
}
// GOOD: Search conversations with filter
const conversations = await client.conversations.search({
query: {
operator: "AND",
value: [
{ field: "state", operator: "=", value: "open" },
{ field: "admin_assignee_id", operator: "=", value: adminId },
],
},
pagination: { per_page: 50 },
});
```
### Step 6: Monitor Request Budget
```typescript
class RequestBudgetMonitor {
private requestsThisMinute = 0;
private resetTime = Date.now() + 60000;
async checkBudget(): Promise<void> {
if (Date.now() > this.resetTime) {
this.requestsThisMinute = 0;
this.resetTime = Date.now() + 60000;
}
this.requestsThisMinute++;
// Warn at 80% of limit
if (this.requestsThisMinute > 8000) {
console.warn(
`[Intercom] High request rate: ${this.requestsThisMinute}/10000 per minute`
);
}
// Hard stop at 95% to prevent 429s
if (this.requestsThisMinute > 9500) {
const waitMs = this.resetTime - Date.now();
console.warn(`[Intercom] Throttling: waiting ${waitMs}ms`);
await new Promise(r => setTimeout(r, waitMs));
}
}
}
```
## Cost Reduction Checklist
- [ ] Replace polling loops with webhooks
- [ ] Cache contact and conversation lookups (5-10 min TTL)
- [ ] Use search instead of list + client-side filter
- [ ] Batch related lookups into single search queries
- [ ] Track API request volume per endpoint
- [ ] Set up alerts at 80% rate limit usage
- [ ] Remove unnecessary API calls in hot paths
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Rate limited (429) | Too many requests | Implement request queuing |
| Stale cached data | TTL too long | Use webhook cache invalidation |
| High infra costs | Queue + retry infrastructure | Reduce request volume first |
| Search too slow | Complex query | Simplify filters, reduce per_page |
## Resources
- [Intercom Pricing](https://www.intercom.com/pricing)
- [Rate Limiting](https://developers.intercom.com/docs/references/rest-api/errors/rate-limiting)
- [Search Contacts](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/contacts/searchcontacts)
## Next Steps
For architecture patterns, see `intercom-reference-architecture`.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.