mcpField
C
check-org-details

check-org-details

github.com/runwaymlDevelopment7447 installsUpdated 2d ago
Repository

About check-org-details

A skill for retrieving and summarizing Runway organization details through its API. It reports credit balance, tier limits, daily generation usage, and optionally historical credit use.

Key features

  1. 01Retrieve organization details
  2. 02Show credit balance and tier
  3. 03Report model rate limits
  4. 04Summarize daily generation counts
  5. 05Query historical credit usage

Use cases

  1. 01Review an organization's remaining credits
  2. 02Check model concurrency and daily limits
  3. 03Track generation usage over time
  4. 04Diagnose API access or quota issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/runwayml/skills --skill check-org-details

After installing, type/check-org-detailsin Claude Code to confirm it loaded.

Details

From the project README

Check Organization Details

PREREQUISITE: Run +setup-api-key first to ensure the API key is configured.

Query the Runway API to retrieve the user's organization details — credit balance, usage tier, rate limits, current daily generation counts, and historical credit usage.

Step 1: Verify API Key Is Available

Before making any requests, confirm the API key is accessible:

  1. Check for a .env file containing RUNWAYML_API_SECRET
  2. Or check if the environment variable is set: echo $RUNWAYML_API_SECRET

If the key is not found, tell the user to run +setup-api-key first and stop.

Step 2: Query Organization Info

Call GET /v1/organization to retrieve the org's tier, credit balance, and current usage.

Node.js
import RunwayML from '@runwayml/sdk';

const client = new RunwayML();
const details = await client.organization.retrieve();
console.log(JSON.stringify(details, null, 2));
Python
from runwayml import RunwayML

client = RunwayML()
details = client.organization.retrieve()
print(details)
cURL / fetch (no SDK)
curl -s https://api.dev.runwayml.com/v1/organization \
  -H "Authorization: Bearer $RUNWAYML_API_SECRET" \
  -H "X-Runway-Version: 2024-11-06" | python3 -m json.tool
Response Shape
{
  "tier": {
    "maxMonthlyCreditSpend": 10000,
    "models": {
      "gen4.5": {
        "maxConcurrentGenerations": 2,
        "maxDailyGenerations": 200
      }
    }
  },
  "creditBalance": 5000,
  "usage": {
    "models": {
      "gen4.5": {
        "dailyGenerations": 12
      }
    }
  }
}

Step 3: Present the Results

Format the output as a clear summary for the user:

## Organization Overview

**Credit Balance:** X credits ($X.XX at $0.01/credit)
**Monthly Spend Cap:** X credits

### Rate Limits (by model)

| Model | Concurrency | Daily Limit | Used Today | Remaining |
|-------|-------------|-------------|------------|-----------|
| gen4.5 | 2 | 200 | 12 | 188 |
| veo3.1 | 2 | 100 | 5 | 95 |
| ... | ... | ... | ... | ... |

Key things to highlight:

  • Credit balance — convert to dollar value (credits × $0.01)
  • Per-model daily limits — show how many generations remain today (rolling 24-hour window)
  • Concurrency — how many tasks can run simultaneously per model
  • Monthly cap — the max credit spend per month for their tier

Step 4 (Optional): Query Credit Usage History

If the user wants to see historical usage, call POST /v1/organization/usage.

Node.js
const usage = await client.organization.retrieveUsage({
  startDate: '2026-02-15',   // ISO-8601, up to 90 days back
  beforeDate: '2026-03-17'   // exclusive end date
});
console.log(JSON.stringify(usage, null, 2));
Python
usage = client.organization.retrieve_usage(
    start_date="2026-02-15",
    before_date="2026-03-17"
)
print(usage)
cURL / fetch (no SDK)
curl -s -X POST https://api.dev.runwayml.com/v1/organization/usage \
  -H "Authorization: Bearer $RUNWAYML_API_SECRET" \
  -H "X-Runway-Version: 2024-11-06" \
  -H "Content-Type: application/json" \
  -d '{"startDate": "2026-02-15", "beforeDate": "2026-03-17"}' \
  | python3 -m json.tool
Response Shape
{
  "results": [
    {
      "date": "2026-03-16",
      "usedCredits": [
        { "model": "gen4.5", "amount": 120 },
        { "model": "veo3.1", "amount": 400 }
      ]
    }
  ],
  "models": ["gen4.5", "veo3.1"]
}

Present this as a usage breakdown:

### Credit Usage (Feb 15 – Mar 17)

| Date | Model | Credits Used |
|------|-------|-------------|
| 2026-03-16 | gen4.5 | 120 |
| 2026-03-16 | veo3.1 | 400 |
| ... | ... | ... |

**Total:** X credits

Tier Reference

If the user asks about upgrading, share the tier breakdown:

TierConcurrencyDaily GensMonthly CapUnlock Requirement
1 (default)1–250–200$100—
23500–1,000$5001 day + $50 spent
351,000–2,000$2,0007 days + $100 spent
4105,000–10,000$20,00014 days + $1,000 spent
52025,000–30,000$100,0007 days + $5,000 spent

Tiers upgrade automatically once the spend and time requirements are met.

Troubleshooting

IssueCauseFix
401 UnauthorizedInvalid or missing API keyRe-run +setup-api-key
creditBalance is 0No credits purchasedPurchase at https://dev.runwayml.com/ → Billing (min $10)
Daily limit reachedRolling 24-hour quota exhaustedWait for the window to reset, or upgrade tier
All models show 0 daily limitTier 1 restrictionsCheck that credits have been purchased

Comments

Markdown supported