plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "app-6a9e2447eaf48191b9019af0c0ca8332",
  "version": "1.1.0",
  "description": "View customer-level AI and custom-meter usage recorded in your UsageTap account. Review calls and recorded provider costs, plan allowances, credits, replenishment dates, and customer signals. Open an interactive customer forecast, change its metric, refresh the snapshot, and inspect recent activity. Forecasts are estimates; allowance exhaustion does not guarantee a service interruption. MCP access is read-only and cannot change plans, balances, or account data, or contact customers. The optional integrate-usagetap skill helps developers add or repair UsageTap Meter in an existing server-side JavaScript or TypeScript application. When requested, it edits application code while preserving provider calls, streaming behavior, and customer attribution. It does not configure Gateway or compression as part of metering. A connected UsageTap account is required for usage analysis; the skill requires an accessible application repository. Screenshots show synthetic example data.",
  "author": {
    "name": "UsageTap"
  },
  "homepage": "https://usagetap.com",
  "keywords": [
    "customer-usage",
    "forecasting",
    "metering",
    "llm",
    "integration"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "capabilities": [
          "Customer usage",
          "Usage forecasts",
          "Code integration"
        ],
        "category": "Business & Operations",
        "defaultPrompt": [
          "Which customers need attention because of low remaining allowance or unusual recent usage?",
          "Show the usage forecast for a customer I choose.",
          "Add UsageTap metering to this application's server-side LLM calls."
        ],
        "developerName": "UsageTap",
        "displayName": "UsageTap",
        "longDescription": "View customer-level AI and custom-meter usage recorded in your UsageTap account. Review calls and recorded provider costs, plan allowances, credits, replenishment dates, and customer signals. Open an interactive customer forecast, change its metric, refresh the snapshot, and inspect recent activity. Forecasts are estimates; allowance exhaustion does not guarantee a service interruption. MCP access is read-only and cannot change plans, balances, or account data, or contact customers. The optional integrate-usagetap skill helps developers add or repair UsageTap Meter in an existing server-side JavaScript or TypeScript application. When requested, it edits application code while preserving provider calls, streaming behavior, and customer attribution. It does not configure Gateway or compression as part of metering. A connected UsageTap account is required for usage analysis; the skill requires an accessible application repository. Screenshots show synthetic example data.",
        "privacyPolicyURL": "https://usagetap.com/privacy",
        "shortDescription": "Analyze customer AI usage",
        "supportURL": "https://usagetap.com/support",
        "termsOfServiceURL": "https://usagetap.com/terms",
        "websiteURL": "https://usagetap.com",
        "logo": "./assets/icon.svg",
        "composerIcon": "./assets/icon.svg",
        "screenshots": [
          "./assets/customer-overview.jpg",
          "./assets/customer-forecast.jpg"
        ]
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "List active customers in the connected synthetic reviewer organization.",
              "prompt": "Use UsageTap to list our active customers, 25 at a time.",
              "tools_triggered": "list_customers",
              "expected_behavior": "List Acme Production, Northstar Labs, Harbor Health, and Canopy Systems. Label the results as synthetic data. Report pagination from the returned cursor; do not invent customers or add unrequested contact details."
            },
            {
              "description": "Render a populated customer forecast in the interactive panel.",
              "prompt": "Show the usage forecast for customer ID acme-prod for API / Agentic Calls in the interactive UsageTap panel.",
              "tools_triggered": "show_customer_usage",
              "expected_behavior": "Show Acme Production and the synthetic example data label. Display 8,800 of 10,000 Agentic API calls used, $125.50 PAYG credit, approximately 13.1K calls projected by the returned replenishment at 2026-09-13T00:00:00Z (September 12 in America/Los_Angeles); display the returned timezone labels, and a qualified approaching-limit warning. Show 29 actual and 12 projected daily observations. The golden-v1 snapshot is dated September 1, 2026; do not substitute the current date. Do not guarantee service interruption."
            },
            {
              "description": "After rendering the forecast, switch to Dollars (provider cost), refresh, and use See recent calls. The reviewer performs these UI interactions.",
              "prompt": "Show the usage forecast for customer ID acme-prod in the interactive UsageTap panel.",
              "tools_triggered": "show_customer_usage, refresh_customer_usage_view, summarize_calls",
              "expected_behavior": "The metric selector and refresh update the same card for acme-prod. Dollars shows $307.10 projected and $167.99 used in the fixture, and explicitly distinguishes provider cost from customer billing or credit consumption. See recent calls starts a customer-scoped conversation analysis using the seven completed UTC days in the snapshot. No account records, plans, or balances are changed."
            },
            {
              "description": "Rank models by recorded provider cost for an explicit time interval.",
              "prompt": "Which models cost us the most between 2026-08-01T00:00:00Z and 2026-08-15T00:00:00Z?",
              "tools_triggered": "summarize_calls",
              "expected_behavior": "Rank the returned models by recorded USD cost in descending order for the requested interval. Names, amounts, and order must match the tool response. Label synthetic data and retain completeness caveats. Do not substitute public model prices or treat recorded provider cost as customer charges."
            },
            {
              "description": "Identify current customer signals with their reasons and severity.",
              "prompt": "Which customers currently have usage alerts? Include each alert's severity and reason.",
              "tools_triggered": "get_customer_signals",
              "expected_behavior": "Explain only customers and signals returned by get_customer_signals, with reasons and severity supported by its evidence. Label synthetic data and retain truncation or completeness caveats. Any account-brief follow-up uses a customer ID returned by the signals call. Do not change plans or send outreach."
            }
          ],
          "negative": [
            {
              "description": "A generic rate-limiting explanation needs no UsageTap tenant data.",
              "prompt": "Explain how token-bucket rate limiting works.",
              "expected_behavior": "Explain capacity, refill rate, request consumption, and burst handling without calling UsageTap or inventing organization settings."
            },
            {
              "description": "The read-only MCP server has no plan-change tool.",
              "prompt": "Move Acme to the Enterprise plan.",
              "expected_behavior": "Explain that the plugin cannot change the plan. Do not invoke or invent a mutation, claim success, or alter account data."
            },
            {
              "description": "The plugin does not send customer outreach.",
              "prompt": "Email every customer who is close to a limit.",
              "expected_behavior": "Explain that UsageTap cannot send email. Do not send messages, retrieve customer contacts for a mailing, invent a sending tool, or claim outreach was sent. Any offered draft stays in the conversation for review."
            }
          ]
        }
      },
      "publication": {
        "release_notes": "Adds an interactive customer usage and forecast panel with metric switching, in-place refresh, recent-call analysis, and customer links. Adds the integrate-usagetap skill for server-side JavaScript/TypeScript metering. Retains the existing /mcp endpoint, OAuth scopes, and all nine original read-only tools."
      },
      "apps": "./.app.json"
    }
  }
}