playbooks

home / skills / jeremylongshore / claude-code-plugins-plus-skills / openrouter-team-setup

openrouter-team-setup skill

/plugins/saas-packs/openrouter-pack/skills/openrouter-team-setup

This skill configures OpenRouter for team and organizational use, enabling multi-user access, per-user controls, and department billing integration.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill openrouter-team-setup

Review the files below or copy the command above to add this skill to your agents.

Files (9)
SKILL.md
1.6 KB
---
name: openrouter-team-setup
description: |
  Configure OpenRouter for team and organizational use. Use when setting up multi-user access or department billing. Trigger with phrases like 'openrouter team', 'openrouter organization', 'multi-user openrouter', 'openrouter rbac'.
allowed-tools: Read, Write, Edit, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Openrouter Team Setup

## Overview

This skill covers setting up OpenRouter for team environments including key management, access control, and usage tracking per user or department.

## Prerequisites

- OpenRouter account with admin access
- Team structure defined

## Instructions

Follow these steps to implement this skill:

1. **Verify Prerequisites**: Ensure all prerequisites listed above are met
2. **Review the Implementation**: Study the code examples and patterns below
3. **Adapt to Your Environment**: Modify configuration values for your setup
4. **Test the Integration**: Run the verification steps to confirm functionality
5. **Monitor in Production**: Set up appropriate logging and monitoring

## Output

Successful execution produces:
- Working OpenRouter integration
- Verified API connectivity
- Example responses demonstrating functionality

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- [OpenRouter Documentation](https://openrouter.ai/docs)
- [OpenRouter Models](https://openrouter.ai/models)
- [OpenRouter API Reference](https://openrouter.ai/docs/api-reference)
- [OpenRouter Status](https://status.openrouter.ai)

Overview

This skill helps configure OpenRouter for team and organizational use, focusing on multi-user access, role-based control, and department-level billing. It guides admins through key management, API integration, and verification steps to ensure secure and auditable usage. The goal is a repeatable setup that fits existing team structures and monitoring practices.

How this skill works

The skill inspects existing OpenRouter account settings and provides patterns for provisioning API keys, assigning roles, and grouping users by department. It includes configuration templates and verification checks to confirm connectivity and expected permissions. Logging and usage-tracking recommendations help enforce quotas and collect billing data per team or project.

When to use it

  • Setting up OpenRouter for a new team or organization
  • Enabling multi-user access with role-based permissions
  • Implementing department or project billing and usage tracking
  • Onboarding new developers who need API keys and scoped access
  • Auditing security and access controls for compliance

Best practices

  • Define team structure and roles before provisioning keys
  • Use scoped API keys per user or service to minimize blast radius
  • Automate key rotation and revoke unused keys promptly
  • Instrument calls with consistent metadata for project and department billing
  • Enable logging and alerts for unusual usage patterns

Example use cases

  • Provision per-department API keys and aggregate usage for chargebacks
  • Set RBAC rules so data scientists have model access while engineers have deployment rights
  • Automate onboarding: create user, issue scoped key, and log assignment
  • Run periodic connectivity and permission checks to avoid production outages
  • Collect usage metrics to forecast spend and enforce quotas

FAQ

Do I need an admin account to run this setup?

Yes. Admin access is required to create API keys, configure roles, and view organization-level usage and billing data.

How do I verify keys and permissions after setup?

Run the included verification checks: test API connectivity, call restricted endpoints to confirm RBAC enforcement, and review logs for a sample user to ensure metadata and billing tags are present.