Do I need API keys to use SkillBoss?

No. SkillBoss works without API keys. Install the skills pack and use one platform across models and services.

Which platforms does SkillBoss support?

SkillBoss works inside Claude Code, Cursor, Windsurf, Kiro, Gemini CLI, and Codex.

How does SkillBoss pricing work?

SkillBoss is pay-as-you-go. Top up your balance and use it across models plus search, scraping, media, email, payments, and deploy workflows.

Can I use Claude Code natively with SkillBoss?

Yes! SkillBoss works as an Anthropic-compatible proxy for Claude Code. Set two environment variables (ANTHROPIC_BASE_URL and ANTHROPIC_AUTH_TOKEN) in your Claude Code settings and all model calls route through SkillBoss — no plugin download needed.

SkillBoss gives AI agents and developers one OpenAI-compatible API for models, search, scraping, voice, video, email, payments, and deploy workflows.

How do I integrate SkillBoss with my AI agent?

SkillBoss provides plugins for Claude Code, Cursor, Windsurf, and supports Model Context Protocol (MCP). You can also use the OpenAI-compatible API endpoint at https://api.skillboss.co/v1 with your API key.

What AI models are available?

SkillBoss supports frontier chat models alongside image, video, and audio generation, plus tool APIs for search, scraping, email, payments, and deploy. Check the live catalog before shipping for the current model list.

How much does SkillBoss cost?

SkillBoss uses pure pay-as-you-go pricing. Add funds to your balance and only pay for what you use. No subscriptions, no monthly fees.

What is the cheapest way to access multiple AI models?

SkillBoss gives you one pay-as-you-go integration across multiple model families and tool APIs, so you can route work without managing separate vendor accounts.

Can I use Claude, GPT, and Gemini with one API key?

Yes. SkillBoss gives you a single API key and OpenAI-compatible endpoint for multiple model families, including Claude, GPT, Gemini, and DeepSeek.

How do I integrate SkillBoss with Claude Code?

Download the SkillBoss skills pack from skillboss.co/download and place in your skills directory. Or use the API directly with the OpenAI-compatible endpoint at api.skillboss.co/v1.

What kinds of work can SkillBoss handle?

SkillBoss covers model calls plus search, scraping, image and video generation, voice, email, payments, hosting, and database workflows for AI agents and developer tools.

What is a multi-AI gateway?

A multi-AI gateway gives you one API and one billing layer across multiple model providers and tool APIs. SkillBoss extends that idea to real agent workflows like search, scraping, voice, payments, email, and deploy.

Does SkillBoss work with OpenClaw?

Yes. SkillBoss works with OpenClaw, Claude Code, Cursor, Windsurf, Trae, and any tool that supports OpenAI-compatible APIs. The API endpoint is api.skillboss.co/v1.

AEO + SEO Playbook

This playbook is for one job: make SkillBoss easier to discover, compare, cite, and adopt across both traditional search engines and AI answer engines.

The target audiences are:

Humans using OpenClaw, Claude Code, Cursor, Windsurf, and similar coding agents.
Developers and teams evaluating an OpenAI-compatible API for production use.
AI agents themselves discovering SkillBoss through docs, manifests, structured data, and machine-readable files.

ℹ️

Traditional SEO wins rankings. AEO wins citations. SkillBoss needs both because the buyer journey now crosses Google, Perplexity, ChatGPT, Claude, Gemini, and agent-run discovery flows.

North Star

The docs should answer three questions better than any competitor:

How do I start using SkillBoss quickly?
Why should I use SkillBoss instead of direct APIs or another gateway?
How can my human team or my AI agent discover the right model, skill, or integration path?

Primary Query Clusters

Cluster	Audience	Example Queries	Best Page Type
Install + setup	Human buyers	`claude code setup`, `openclaw setup`, `skillboss quickstart`	Installation docs, quick start
Alternatives + migration	Human buyers	`claude code alternative`, `openrouter alternative`, `openclaw alternatives`	Comparison pages, migration guides
API + technical validation	Developers	`openai compatible api`, `multi model api`, `usage api`, `chat completions api`	API reference, SDK docs, partner docs
Use-case intent	Builders	`best ai model for coding`, `send email api for ai agents`, `stripe api for agents`	Use-case docs, tutorial docs
Agent discovery	AI agents	`llms.txt`, `agent.json`, `mcp manifest`, `tool discovery`	For AI Agents, agent discovery docs, manifests

Content Strategy by Audience

1. OpenClaw / Claude Code / coding-agent users

These users usually search with one of four intents:

setup
cheaper / faster model access
better model catalog
alternatives / comparisons

Pages that should carry this demand:

2. API buyers and partner teams

These visitors care about integration speed, compatibility, pricing clarity, and operational trust.

Pages that should carry this demand:

3. AI agents and agent-run evaluation flows

These systems optimize for extractable answers, manifests, structured data, and machine-readable files.

Priority discovery assets:

For AI Agents
Agent Discovery
llms.txt
llms-full.txt
agent.json
openapi.json
skill.md

What Good Pages Must Include

Every strategic docs page should satisfy this checklist:

Clear answer in the first 2 paragraphs
A title that matches how a real buyer phrases the query
A short, literal implementation path
Internal links to the next decision page
At least one FAQ block when the page targets comparison, setup, or objections
Machine-readable metadata that reflects the actual page topic
A current date or freshness signal when the page can age quickly

Page Templates We Should Favor

Setup pages

Use for installation and onboarding queries.

Lead with the exact setup outcome
Include prerequisites
Include copy-paste commands
Include troubleshooting FAQs
Link to pricing, API docs, and agent-specific pages

Comparison pages

Use for X vs Y, alternative, better than, and migration queries.

Lead with the decision summary
Include an explicit comparison table
Separate who should choose SkillBoss vs who should not
Link to quick start, pricing, and integration docs

Use-case pages

Use for jobs-to-be-done and high-intent product exploration.

Lead with the use case and outcome
List the exact APIs/models/skills involved
Include a minimal architecture block
Link to API reference and install docs

Agent-discovery pages

Use for AI-native visibility.

Explain the machine-readable file or manifest first
Include direct examples that an agent can lift verbatim
Use stable URLs and compact explanations
Keep docs internally linked to manifests and model catalogs

Internal Linking Playbook

Links should move users from awareness to activation:

Awareness pages should link to a setup page and a comparison page.
Setup pages should link to pricing, troubleshooting, and one use-case page.
API reference pages should link to quick start, usage, and catalog pages.
Agent discovery pages should link to manifests, API docs, and the main catalog.

Bad pattern:

isolated docs pages that rank for a narrow keyword but do not move readers deeper into the product

Good pattern:

every page links to the next implementation or purchase decision

Structured Data + Metadata Standards

For docs pages, the baseline should be:

canonical URL
Open Graph + Twitter metadata
TechArticle schema
BreadcrumbList schema
FAQPage schema whenever the page includes real FAQs
keyword metadata aligned to the page intent

For AEO, the most important property is not “more schema everywhere.” It is schema that matches an actually extractable page.

AEO Writing Rules

Use these on any docs page that should be cited by ChatGPT, Perplexity, Claude, Gemini, or Google AI Overviews:

Answer first, explain second
Keep the first answer block self-contained
Use direct language, not marketing filler
Put product names and integration terms in natural language headings
Use tables for comparisons
Use FAQs for objections and edge cases
Keep implementation examples current and copy-pasteable
Use stable naming for models, routes, and manifests

Quarterly Content Priorities

These are the highest-value docs clusters for SkillBoss SEO/AEO growth:

Claude Code setup, migration, troubleshooting, and alternatives
OpenClaw setup, model choice, cost optimization, and alternatives
OpenAI-compatible API reference and migration pages
AI agent discovery pages around llms.txt, MCP, and manifest-based discovery
High-intent use cases where SkillBoss compresses multiple tools into one integration

Measurement Framework

Track performance in three buckets:

Traditional SEO

impressions
clicks
CTR
ranking movement for priority queries
organic entries to install / API / pricing pages

AEO / answer engine visibility

citations in Perplexity, ChatGPT, Claude, Gemini
share of mentions vs direct competitors
frequency of being cited on comparison and setup queries

Activation quality

visits from docs to /console
visits from docs to /catalog
visits from docs to /pricing
partner inquiries from docs
API key creation and usage after docs entry

Editorial Cadence

Weekly

refresh stale screenshots or setup commands
review broken internal links
update one high-intent page in the Claude Code / OpenClaw cluster

Monthly

rewrite at least one comparison page and one use-case page
audit FAQ quality on top-entry docs pages
update internal links from blog pages to activation pages

Quarterly

re-evaluate the top query clusters
add missing comparison pages
refresh titles and descriptions for strategic docs
verify machine-readable files still reflect the docs truthfully

Common Failure Modes

Publishing technically correct docs that do not target a real query. Search engines and AI answer engines reward pages that clearly match a user intent, not just pages that exist.

Assuming manifests and llms files are enough on their own. They help agent discovery, but human-readable docs still need clear answers, comparisons, FAQs, and internal links so both humans and AI systems can trust and cite the site.

Start with the pages closest to revenue: quick start, Claude Code setup, OpenClaw integration, API overview, API catalog, pricing-adjacent use cases, and partner quick start.

Write for a human decision-maker first, but structure each section so it can be extracted as a standalone answer. That means concise lead paragraphs, literal headings, tables, FAQs, and stable terminology.

Immediate Next Actions

Keep the docs sidebar free of broken routes.
Add keyword coverage and FAQ schema support at the docs template level.
Prioritize the Claude Code, OpenClaw, API, and partner docs cluster for ongoing refreshes.
Treat docs as both a product surface and a search surface.