Pre-Install Partner Quick Start

This is the only partner onboarding doc you need.

If you are embedding SkillBoss into your own product, the current integration surface is:

• OpenAI-compatible API base URL: https://api.skillboss.co/v1
• Auth: Authorization: Bearer <your_skillboss_key>
• Account usage API: GET https://www.skillboss.co/api/me/usage
• Current public API catalog: API Catalog
• Current API + skills browser: Catalog

What You Get

• One server-side integration for the current SkillBoss API catalog
• OpenAI-compatible chat completions for your product UX
• Account-level usage reporting via /api/me/usage
• End-user attribution support via the user field on OpenAI-compatible requests
• Public catalog pages you can send users to when they want to browse APIs or skills

Self-Service Onboarding

You should be able to complete the initial partner integration without waiting on us.

The fastest self-service path is:

1. Create an account at skillboss.co/console.
2. Generate or copy your API key.
3. Integrate SkillBoss server-side inside your product.
4. Pass your own customer ID in the user field.
5. Validate usage with /api/me/usage.

Use [email protected] if you want launch support, higher-volume coordination, or help debugging an issue.

Step 1: Make Your First Request

Use the SkillBoss base URL with the official OpenAI SDK.

from openai import OpenAI

client = OpenAI(
    api_key="YOUR_SKILLBOSS_KEY",
    base_url="https://api.skillboss.co/v1",
)

response = client.chat.completions.create(
    model="claude-4-5-sonnet",
    messages=[{"role": "user", "content": "Hello from our product"}],
)

print(response.choices[0].message.content)

Step 2: Attach Your End User ID

If you sell credits or usage inside your own product, pass your internal customer ID through the OpenAI-compatible user field.

response = client.chat.completions.create(
    model="claude-4-5-sonnet",
    messages=[{"role": "user", "content": "Summarize this document"}],
    user="customer_12345",
)

Use that same ID in your own billing, logging, and analytics pipeline so each request is attributable to the correct customer in your app.

Step 3: Read Usage Programmatically

Your partner account can query its own usage with the same API key.

curl -H "Authorization: Bearer YOUR_SKILLBOSS_KEY" \
  "https://www.skillboss.co/api/me/usage?period=day"

import requests

usage = requests.get(
    "https://www.skillboss.co/api/me/usage",
    headers={"Authorization": "Bearer YOUR_SKILLBOSS_KEY"},
    params={"period": "month"},
).json()

print(usage["summary"]["total_requests"])
print(usage["summary"]["total_usd"])

Supported query parameters in the current site route:

• period: day, week, month, all
• model: partial model filter
• type: category filter like chat, image, video, audio, scraper, search

Reference: Usage API

Recommended Integration Pattern

Server-side proxy

This is the recommended default for partner integrations.

1. Your frontend talks only to your backend.
2. Your backend stores the SkillBoss API key.
3. Your backend calls SkillBoss with user=<your_customer_id>.
4. Your app charges the customer using your own credits, wallet, or subscription rules.

from flask import Flask, request
from openai import OpenAI

app = Flask(__name__)

client = OpenAI(
    api_key="YOUR_SKILLBOSS_KEY",
    base_url="https://api.skillboss.co/v1",
)

@app.route("/api/chat", methods=["POST"])
def chat():
    customer_id = request.json["customer_id"]
    message = request.json["message"]

    result = client.chat.completions.create(
        model="claude-4-5-sonnet",
        messages=[{"role": "user", "content": message}],
        user=customer_id,
    )

    return {"reply": result.choices[0].message.content}

Current Technical Baseline

Common Integration Blockers

These are the issues partners are most likely to hit during implementation:

• Using api.heybossai.com in new code instead of api.skillboss.co
• Calling SkillBoss directly from the browser instead of server-side
• Not sending your internal customer ID in the user field
• Expecting /api/me/usage to return partner-side per-customer reconciliation data
• Shipping with stale model IDs instead of checking /docs/api-catalog or GET /models
• Using the wrong endpoint shape for the model you selected
• Launching without testing both a success path and an auth failure path

If You Get Stuck

If your team finds an issue, contact [email protected].

Include:

• Your product name
• Environment (local, staging, or prod)
• Endpoint used
• Model ID used
• Approximate timestamp
• Error message or response payload

That gives us enough context to diagnose the issue quickly.

Common FAQ