miro-cost-tuning
Optimize Miro API costs through credit monitoring, request reduction, and plan selection based on the credit-based rate limiting model. Trigger with phrases like "miro cost", "miro billing", "reduce miro costs", "miro pricing", "miro credits usage".
What this skill does
# Miro Cost Tuning
## Overview
Miro's API pricing is based on your plan tier (Free, Business, Enterprise), not per-API-call billing. However, the **credit-based rate limiting** system (100,000 credits/minute) effectively caps throughput. Cost optimization means minimizing API calls to stay within your plan's rate limits and reduce the need for higher-tier upgrades.
## Miro Plan Comparison
| Feature | Free | Business | Enterprise |
|---------|------|----------|------------|
| Price | $0/user | $12-20/user/mo | Custom |
| Boards | 3 editable | Unlimited | Unlimited |
| API access | Yes | Yes | Yes |
| Rate limit | 100K credits/min | 100K credits/min | Higher (negotiable) |
| OAuth scopes | All standard | All standard | All + enterprise scopes |
| SCIM provisioning | No | No | Yes |
| Audit logs API | No | No | Yes |
| SSO/SAML | No | No | Yes |
## Credit Usage Tracking
```typescript
class MiroUsageTracker {
private minuteCredits = 0;
private dailyRequests = 0;
private minuteStart = Date.now();
private dailyStart = Date.now();
trackRequest(response: Response): void {
// Reset minute window
if (Date.now() - this.minuteStart > 60_000) {
this.minuteCredits = 0;
this.minuteStart = Date.now();
}
// Reset daily window
if (Date.now() - this.dailyStart > 86_400_000) {
this.dailyRequests = 0;
this.dailyStart = Date.now();
}
const limit = parseInt(response.headers.get('X-RateLimit-Limit') ?? '100000');
const remaining = parseInt(response.headers.get('X-RateLimit-Remaining') ?? '100000');
this.minuteCredits = limit - remaining;
this.dailyRequests++;
}
getReport(): UsageReport {
return {
currentMinuteCredits: this.minuteCredits,
creditUtilizationPercent: Math.round((this.minuteCredits / 100000) * 100),
dailyRequests: this.dailyRequests,
projectedMonthlyRequests: this.dailyRequests * 30,
recommendation: this.getRecommendation(),
};
}
private getRecommendation(): string {
if (this.minuteCredits > 80000) {
return 'CRITICAL: >80% credit usage. Reduce request rate or upgrade to Enterprise.';
}
if (this.minuteCredits > 50000) {
return 'WARNING: >50% credit usage. Consider caching and batching.';
}
return 'Healthy credit usage.';
}
}
```
## Cost Reduction Strategies
### Strategy 1: Reduce Read Requests with Caching
The biggest cost saver. Most Miro board reads return data that changes infrequently.
```typescript
// EXPENSIVE: Fetching board on every page load
app.get('/dashboard', async (req, res) => {
const board = await miroFetch(`/v2/boards/${boardId}`); // 1 credit per load
const items = await miroFetch(`/v2/boards/${boardId}/items`); // 1 credit per load
res.render('dashboard', { board, items });
});
// OPTIMIZED: Cache board data for 2 minutes
app.get('/dashboard', async (req, res) => {
const board = await getCachedBoard(boardId); // Cache hit = 0 credits
const items = await getCachedItems(boardId); // Cache hit = 0 credits
res.render('dashboard', { board, items });
});
// With webhook-driven invalidation, cache hits can be 95%+
// That is a 20x reduction in API calls
```
### Strategy 2: Filter Items by Type
Don't fetch all items if you only need sticky notes.
```typescript
// EXPENSIVE: Fetch all items, filter client-side
const allItems = await miroFetch(`/v2/boards/${boardId}/items?limit=50`);
const notes = allItems.data.filter(i => i.type === 'sticky_note');
// OPTIMIZED: Server-side type filter
const notes = await miroFetch(`/v2/boards/${boardId}/items?type=sticky_note&limit=50`);
// Fewer items returned = smaller response = faster
```
### Strategy 3: Batch Writes with Controlled Concurrency
```typescript
// EXPENSIVE: Sequential writes (slow + same credits)
for (const note of notes) {
await createStickyNote(boardId, note); // 200ms * 50 = 10 seconds
}
// OPTIMIZED: Parallel with concurrency control (same credits, 5x faster)
import PQueue from 'p-queue';
const queue = new PQueue({ concurrency: 5 });
for (const note of notes) {
queue.add(() => createStickyNote(boardId, note));
}
await queue.onIdle(); // ~2 seconds
```
### Strategy 4: Use Webhooks Instead of Polling
```typescript
// EXPENSIVE: Poll every 10 seconds (8,640 requests/day)
setInterval(async () => {
const items = await miroFetch(`/v2/boards/${boardId}/items`);
detectChanges(items);
}, 10_000);
// OPTIMIZED: Webhook subscription (0 polling requests)
// Miro pushes changes to your endpoint in real-time
// See miro-webhooks-events for setup
```
### Strategy 5: Smart Pagination Limits
```typescript
// WASTEFUL: Small page size = more round trips
let cursor;
do {
const page = await miroFetch(`/v2/boards/${boardId}/items?limit=10&cursor=${cursor ?? ''}`);
// 10 items per page = 10 requests for 100 items
} while (cursor);
// OPTIMIZED: Max page size
let cursor;
do {
const page = await miroFetch(`/v2/boards/${boardId}/items?limit=50&cursor=${cursor ?? ''}`);
// 50 items per page = 2 requests for 100 items
} while (cursor);
```
## Usage Dashboard Query
If you track API calls in a database:
```sql
SELECT
DATE_TRUNC('hour', created_at) AS hour,
endpoint,
COUNT(*) AS requests,
AVG(duration_ms) AS avg_latency_ms,
COUNT(*) FILTER (WHERE status = 429) AS rate_limited
FROM miro_api_logs
WHERE created_at >= NOW() - INTERVAL '24 hours'
GROUP BY 1, 2
ORDER BY requests DESC;
```
## Budget Alerts
```typescript
// Alert when approaching credit limit
const tracker = new MiroUsageTracker();
// After each API call
tracker.trackRequest(response);
const report = tracker.getReport();
if (report.creditUtilizationPercent > 80) {
await sendSlackAlert({
channel: '#engineering-alerts',
text: `Miro API credit usage at ${report.creditUtilizationPercent}%. ${report.recommendation}`,
});
}
```
## When to Upgrade to Enterprise
Consider Enterprise if you need:
- Higher rate limits (negotiated per account)
- SCIM API for automated user provisioning
- Audit logs API for compliance
- Organization-level management endpoints
- SSO/SAML integration APIs
- Dedicated support for API issues
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Hitting 429 frequently | Too many requests | Implement caching + webhooks |
| Credit spikes | Runaway polling loops | Audit all `setInterval` calls |
| Unnecessary full-board fetches | No type filtering | Add `?type=` parameter |
| Small page sizes | Low `limit` parameter | Use `limit=50` (maximum) |
## Resources
- [Miro Pricing](https://miro.com/pricing/)
- [Rate Limiting](https://developers.miro.com/reference/rate-limiting)
- [Miro Enterprise](https://miro.com/enterprise/)
## Next Steps
For architecture patterns, see `miro-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.