Product Guides

Choose models and connect your apps.

Use Models to see the aliases currently available to your account. Use Connectors to authorize the services Kendr may read or act on for your tasks.

Open Models Open Connectors

Choose a Kendr model

The Models screen shows each public alias, capability, context size, current credit rate, and availability. Choose the alias by outcome rather than assuming a vendor model will always remain available.

ModeUse it forWhat to expect
NormalDirect chat, generation, structured output, vision, web search, and compatible tools.A stable Kendr alias maps the request to an available model route.
IntelligentTasks that benefit from model selection, streaming status, web search, or independent verification.Kendr may select and verify work before returning the final response.
SpecializedCapabilities such as media, search, or other purpose-specific workflows.The request and response contract depends on that feature.
 
curl https://kendr.org/v1/models \
  -H "Authorization: Bearer $KENDR_API_KEY"
Runtime discovery

Read GET /v1/models when your application starts or refreshes its model picker. Do not assume every alias is available to every account at all times.

Web search capability

Text aliases can expose web_search. Use web_search: false on a model request when a prompt should not use current web information.

Supported model-provider families

Kendr aliases may be backed by the provider families below. Your application still sends a Kendr key and Kendr alias; it does not send a separate provider credential.

Provider keyFamily
bedrockAmazon Bedrock-compatible model routes
openaiOpenAI model families
anthropicAnthropic Claude model families
googleGoogle Gemini model families
xaixAI model families
deepseekDeepSeek model families
zaiZ.ai model families
qwenQwen model families
kimiKimi model families
mistralMistral model families

For Bedrock-backed model calls, BEDROCK_MODEL_REGION controls the model invocation region. AgentCore Gateway Web Search is configured separately with AGENTCORE_GATEWAY_REGION and is currently expected to be us-east-1.

Connect an app to Kendr

  1. 1
    Open Connectors
    Sign in and go to Account → Connectors.
  2. 2
    Choose a service
    Select a service marked ready for connection and review what it can provide.
  3. 3
    Continue to the provider
    Sign in to that service and review the requested scopes on its consent page.
  4. 4
    Approve only what you need
    Complete consent only if the account, scopes, and Kendr connection are correct.
  5. 5
    Return to Kendr
    Confirm the connector now shows Connected, then run a read-only task first.
Actions remain explicit

A connected app can provide context and tools, but you should still review sends, edits, creates, deletes, purchases, and other consequential actions before allowing them.

App connector catalog

Google Workspace
Gmail, Drive, Calendar, and related workspace context when available.
Microsoft 365
Mail, calendar, files, and collaboration services for the signed-in Microsoft account.
GitHub
Repositories, issues, pull requests, Actions, and development context.
Slack
Workspace search, channels, threads, and approved message actions.
Notion
Pages, databases, and workspace knowledge within granted access.
Atlassian Cloud
Jira and Confluence context for projects, work items, and documentation.
Salesforce
Customer and CRM context within the scopes approved by the account.
Figma
Design files, comments, and product-design context when supported.
Airtable
Bases and structured records available to the connected account.

Disconnect or reconnect

  • Open Connectors and choose Disconnect when Kendr should no longer use that service.
  • Revoke Kendr from the service's own connected-app settings when you want to end the authorization at the provider as well.
  • Reconnect after a token expires, permissions change, or you need to use a different account.
  • If a task cannot find expected data, confirm the connected identity and granted scopes before adding broader access.