Use separate headers for API key and partner email:
Standard Authorization header compatible with MCP client tools:
💡 Tip: When you create an API key in the partner portal, we automatically generate the Authorization header for you!
Three hosts, and they are not interchangeable. The /mcp/* endpoints on this page live on the analytics service at analytics.knotie-ai.pro and use the header / Basic scheme above. The Partner MCP Gateway and Partner REST API live on mcp.knotie-ai.pro and take your pkt_ key as Authorization: Bearer — never Basic. Partner routes under /api/partner/ (including customer onboarding) are on the main app at knotie-ai.pro or your own white-label domain. Each entry below shows the host it actually needs.
https://analytics.knotie-ai.pro/mcp/capabilitiesRetrieve available MCP capabilities and partner information
X-API-KeyRequiredpkt_your_api_keyX-Partner-EmailRequired[email protected]{
"partner_id": "uuid",
"partner_name": "Your Business Name",
"partner_email": "[email protected]",
"capabilities": [
{
"name": "create_customer",
"description": "Create new customers",
"endpoint": "/mcp/customers"
}
],
"total_capabilities": 6,
"last_updated": "2024-01-01T00:00:00Z"
}curl -X GET \ -H "X-API-Key: pkt_your_api_key" \ -H "X-Partner-Email: [email protected]" \ https://analytics.knotie-ai.pro/mcp/capabilities
curl -X GET \ -H "Authorization: Basic your_auth_token" \ https://analytics.knotie-ai.pro/mcp/capabilities
💡 Note: Replace "your_auth_token" with the Authorization header generated in your partner portal when creating an API key.