Overview

These APIs back the Token Factory screens: browsing models, issuing and deleting virtual-key tokens, starting playground conversations, creating and managing members, creating departments and teams, reading the audit log, managing model owners, and loading the token cost estimation application.

Base URL

https://{your-tenant-host}/api/v1

Use the same Monetize360 tenant host as the Mbrix and Revos APIs.

Authentication

Send a tenant Bearer token (the JWT from signing in to Monetize360):

curl -H "Authorization: Bearer YOUR_API_TOKEN" \
  "https://YOUR_TENANT_HOST/api/v1/model-catalog?page=0&size=20"

That token is the platform session token. The virtual-key JWT returned by Keys is a different credential: applications send it to the AI gateway, and it is not the token that calls these management APIs.

Member create, update, and delete require one of ORG_ADMIN, SUPERADMIN, TENANTADMIN, or ROLE_SYSTEM.

Endpoint groups

Paths above are relative to /api/v1.

Pagination

Catalog and vendor lists return StandardPageResponse. size is clamped to 1–100.

{
  "items": [],
  "page": 0,
  "size": 20,
  "totalElements": 0,
  "totalPages": 0
}

Member and audit lists return a Spring Page (content, totalElements, totalPages, number, size). Page indexes are 0-based.

Department and team lists use POST .../resolved-data. Pagination sits in the JSON body (pagination.page, pagination.size), and the response uses data plus meta.

Errors