Partner Program — Get Started

The Partner Program lets your organization publish skills and workflows into the Phoenix catalog so other customers can discover and run them. You drive the entire publishing flow from your own AI client (Claude Desktop, Claude.ai, ChatGPT, or any MCP-capable tool) by calling the admin MCP — no Phoenix UI needed after the first key is minted.

This page gets you connected. From there:

• Tool Reference — the five submission tools, in pipeline order
• Lifecycle — submission states, AI-review rubric, the autopublish gate
• Troubleshooting — what every error code means and how to fix it

What publishing means

A successful submission turns into a row in the Phoenix catalog flagged partnerOwned = true, attributed to your organization. Customers see it alongside HG Insights' first-party skills and workflows. You retain ownership; Phoenix handles distribution, billing, and the AI-safety review.

There are two artifact types:

Type	What it is	Submitted via
Skill	A reusable knowledge or task module (markdown body + tool allowlist) that any agent can compose with	admin_submit_skill
Workflow	A prompt-driven multi-step agent with required MCP servers and recommended skills	admin_submit_workflow

Step 1: Mint an admin-scoped API key

Partner publishing requires an admin-scoped API key. Phoenix has two scopes:

• user — the default. Can call customer-facing MCP tools.
• admin — additionally exposes the partner-submission tools and admin operations.

The scope is stored on the key itself; minting a new admin key is the only way to obtain admin access — you cannot promote an existing user key.

To mint one:

1. Sign in to https://phoenix.hginsights.com as an organization admin. (Only org admins can issue admin-scoped keys.)
2. Open Settings → API Keys.
3. Click New API Key.
4. Set Scope to admin.
5. Copy the displayed key value immediately — Phoenix only shows it once.

Treat admin keys like production credentials: store them in your secret manager, rotate them on a schedule, and never commit them.

Step 2: Point your client at the admin MCP

The admin MCP lives at the same endpoint as the customer MCP:

https://phoenix.hginsights.com/api/mcp

What changes is the header: include your admin key, and the server exposes both the customer tools and the five admin_* submission tools through the same MCP handshake.

Two equivalent auth headers are accepted:

Header	When to use
x-api-key: <admin_key>	Preferred. Works in all clients and is required by Azure APIM / the Power Automate connector.
Authorization: Bearer <admin_key>	Standard OAuth-style header. Use when your client only supports Authorization.

Both route through the same validateApiKeyBearer flow; billing and rate limits are identical.

When the client's tools/list handshake completes, your tool inventory includes:

• admin_submit_skill
• admin_submit_workflow
• admin_validate_submission
• admin_test_submission
• admin_request_review

If those tools are missing, the key is not admin-scoped — see Troubleshooting → 403 forbidden_admin_scope.

Step 3: Connect from your client

The configuration patterns mirror the customer MCP-client setup guide; only the auth header differs.

Claude Desktop

Edit your claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "phoenix-admin": {
      "transport": "http",
      "url": "https://phoenix.hginsights.com/api/mcp",
      "headers": {
        "x-api-key": "<YOUR_ADMIN_KEY>"
      }
    }
  }
}

Restart Claude Desktop. In any chat, ask "what Phoenix admin tools are available?" — Claude should list the five admin_* tools.

Claude.ai (web)

Claude.ai's MCP connectors UI accepts API-key servers in Settings → Integrations → Add custom integration:

• URL: https://phoenix.hginsights.com/api/mcp
• Authentication: Custom header
  • Header name: x-api-key
  • Header value: <YOUR_ADMIN_KEY>

After Claude.ai completes the tools/list handshake, the five admin_* tools appear in the connector's tool inventory.

ChatGPT (Apps SDK)

ChatGPT's Apps SDK supports custom MCP servers in Developer mode → Apps & Connectors → Custom:

• Server URL: https://phoenix.hginsights.com/api/mcp
• Authentication: Bearer token → <YOUR_ADMIN_KEY>

ChatGPT's Apps SDK uses SSE transport with Accept: text/event-stream; Phoenix's /api/mcp endpoint speaks both transports automatically — no client-side change needed.

Anything else

Any MCP client that supports streamable HTTP plus a custom header will work. The handshake is the standard MCP initialize → tools/list flow. If tools/list returns fewer than five admin_* tools, see Troubleshooting.

Next steps

You're connected. Pick a path:

• First-time partner: read Tool Reference end-to-end, then call admin_submit_skill (or admin_submit_workflow) with a draft payload.
• Understanding the review pipeline: read Lifecycle — covers the state machine, the AI-review rubric, and what triggers an autopublish vs. a manual hold.
• Debugging an error: jump to Troubleshooting and search for the error code Phoenix returned.