Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.knotie-ai.pro/llms.txt

Use this file to discover all available pages before exploring further.

​
Start here first

If you are looking for the current OpenAI-compatible API key flow, use the top-level AI Gateway page. That is where partners now:
  • Create virtual LLM keys
  • Control model access
  • Manage budgets and top-ups
  • Regenerate or revoke keys
  • Configure customer self-service AI Gateway access

​
Which option to use

​
AI Gateway

Use AI Gateway when you need:
  • OpenAI-compatible virtual keys
  • Model restrictions
  • Metered LLM usage
  • Customer-billed AI Gateway keys
  • Customer self-service key creation from the whitelabel portal

​
Customer portal API Keys

Use the customer-side API Keys menu when a customer needs standard programmatic access that depends on:
  • API Access being enabled
  • API Keys menu visibility being enabled
This is separate from AI Gateway.

​
MCP Tokens

Use MCP Tokens when you are working with MCP-specific integrations and agent tooling.

​
Embed URLs

Use Embed URLs for:
  • Customer-scoped widgets
  • Embedded portal experiences
  • iframe or embedded access flows
Do not use a partner AI Gateway key for embedded customer portal access.

​
Security reminders

Treat any key or token like a password:
  • Never expose it in client-side code unless that flow is specifically designed for browser use
  • Store it in a secrets manager or password vault
  • Rotate it after team changes or suspected exposure

​
Common confusion to avoid

  • AI Gateway is for metered LLM access.
  • API Keys visibility in the client portal depends on API Access.
  • AI Gateway visibility in the client portal depends on AI Credits plus the partner self-service setting.
  • Embed URLs are for embedded customer experiences, not server-side partner automation.