com um clique
chat2api-management-api
// Use when operating Chat2API Manager's management API for testing, including health checks, config snapshots, temporary API keys, model mappings, sessions, logs, and cleanup verification.
// Use when operating Chat2API Manager's management API for testing, including health checks, config snapshots, temporary API keys, model mappings, sessions, logs, and cleanup verification.
Use when converting OpenAI-compatible client HAR files into sanitized replayable Chat2API tool-calling fixtures.
Use when running Chat2API provider and model matrix tests using live /v1/models discovery and management API attribution.
Use when validating Chat2API Manager proxy behavior across dialogue, tool calling, context, provider routing, request logs, and live client replay workflows.
Use when replaying sanitized client tool-calling fixtures against Chat2API with client-specific pass/fail rules.
| name | chat2api-management-api |
| description | Use when operating Chat2API Manager's management API for testing, including health checks, config snapshots, temporary API keys, model mappings, sessions, logs, and cleanup verification. |
Use this skill before live proxy testing that needs /v0/management/*.
Use scripts/management-api.mjs for repeatable management API setup, observation, and cleanup commands.
CHAT2API_MGMT_SECRET=mgmt_xxx node skills/chat2api-management-api/scripts/management-api.mjs snapshot
CHAT2API_MGMT_SECRET=mgmt_xxx node skills/chat2api-management-api/scripts/management-api.mjs create-api-key --name codex-live-test
CHAT2API_MGMT_SECRET=mgmt_xxx node skills/chat2api-management-api/scripts/management-api.mjs delete-api-key --id key-id
CHAT2API_MGMT_SECRET=mgmt_xxx node skills/chat2api-management-api/scripts/management-api.mjs restore-tool-config --file /private/tmp/toolCallingConfig.json
Use --dry-run to verify command shape without network calls.
create-api-key prints a one-time API key to stdout. Do not write this output to durable logs, transcripts, or shared artifacts.
snapshot omits request logs by default. Use snapshot --include-logs only when logs are intentionally needed; included snapshot data is locally redacted before printing.