Skip to main content
These answers cover what partners ask most once an AI coding agent is writing Suki integration code: where credentials and environments come from, how to keep the agent accurate, and how to fix common failures. For setup, start with AI coding tools.

Build with an agent

From you. Suki issues your Partner ID during Partner onboarding, and your identity provider issues the Partner Token JWT. Agents cannot create credentials, and Suki skills tell the agent to stop and point you to onboarding when credentials are missing. Keep tokens out of source code and version control, and never expose sdp_suki_token in client-side code or logs.
Staging, until you are ready for production. Skills and integration prompts tell agents to use staging unless you ask for production.SDKs take an environment option instead of a URL, for example environment: "staging" on SukiAuthManager. Your Partner Token, hosts, and SDK environment must all point at the same environment.
The Partner API spec is at https://developer.suki.ai/api-reference/openapi.json. It covers authentication, Ambient, Form filling, Dictation transcription, Patient Summary and CKG ingestion, info endpoints, webhooks, and the /ws/stream and /ws/transcribe WebSocket endpoints. SDKs are not in the spec. Agents should use the SDK API reference pages and skills for those.
Load the product skill first, connect the Documentation MCP, and start from an Integration prompt. Skills include accuracy rules that forbid invented endpoints, SDK methods, and message types. Integration prompts also tell the agent to check every field against the docs or the OpenAPI spec, mark anything it cannot find as BLOCKED, and report untested cases as Not run. Review those items before you ship.
Ambient and Form filling stream audio on /ws/stream. Dictation streams on /ws/transcribe with different message shapes. Agents often mix these up, so name the product in your prompt. Refer to Streaming architecture.

Fix agent output

A 401 has two common causes. Suki rejected the Partner Token at Register or Login, or a later call sent a missing, expired, or invalid Suki Token. Login returns suki_token, and later REST and WebSocket calls must send it as the sdp_suki_token header. Refer to 401 Unauthorized or invalid Partner Token.
The Partner Token, REST and WebSocket hosts, and SDK environment probably point at different environments. Refer to Wrong staging vs production endpoints.
Agents connected to the Documentation MCP can report a page with the submit feedback tool, and the docs team reviews that feedback. You can also contact support.

Next steps

Integration prompts - Copy-ready prompts for each workflow, SDK, and API. Agent skills - Install every product skill with one command. Documentation MCP - Live doc search in your editor.
Last modified on October 26, 2026