Suki bronze
developer.suki.ai
we checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 11 Jan 2027 as of our check on 10 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR1 under ISRG Root X1 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
developer.suki.ai. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 10 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI use policy
-
What this site's
robots.txtsays about how AI may use its content. Recorded as the operator wrote it, not enforced β these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents. - AI-facing documents
-
Publishes
/llms.txtβ “Suki” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 13 Oct 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· Amazon.com, Inc. (AS16509)
- Last checked
- 5d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of developer.suki.ai controls every word below.
suki-ambient-api
Use for direct Partner Ambient APIs (not SDKs): authenticate, create an Ambient session, provide session context, stream visit audio on /ws/stream, end the session, poll status, and retrieve clinical note content or transcript. Do not use for Web SDK, Headless Web SDK, or Mobile SDK.
suki-ambient
Use when building ambient clinical documentation with Suki Ambient APIs or Ambient SDKs, including Web SDK, Headless Web SDK, and Mobile SDK: create an Ambient session, provide session context, stream visit audio, end the session, and retrieve generated clinical note content.
suki-audio-streaming
Use when implementing or debugging Suki Partner WebSocket audio streaming for Ambient, Form filling, or Dictation, including WebSocket authentication, JSON message formats, audio encoding, stream lifecycle, and end-of-stream handling.
suki-dictation-api
Use for direct Partner Dictation APIs (not SDKs): authenticate, create a transcription session, stream PCM over /ws/transcribe with audioData frames and AUDIO_END, handle partial and final transcripts (is_final), end the session, and optionally rewrite selected text with POST /api/v1/content/rewrite (CONCISE, VERBOSE, or PATIENT_FRIENDLY). Do not use for Dictation SDK or Web SDK Dictation embeds.
suki-dictation-sdk
Use when embedding hosted Suki Dictation with @suki-sdk/dictation or @suki-sdk/dictation-react: SukiAuthManager, one reusable DictationClient, DictationProvider in React, in-field and scratchpad modes, Content Rewrite in the hosted UI (no new ShowOptions), and onSubmit / onCancel callbacks. Prefer this over raw /ws/transcribe for browser Dictation UI. Distinct from Web SDK built-in Dictation and the Dictation Partner API.
suki-dictation
Use when building real-time clinical Dictation with Suki: embed Dictation with the Dictation SDK or Web SDK, or use the Dictation APIs to create a transcription session, stream PCM audio over /ws/transcribe, receive partial and final transcript text, and end the session.
suki-em-coding-api
Use for direct Partner E/M Coding APIs: authenticate, POST /api/v1/em-codes with note sections, poll status, retrieve em_codes.values, and handle the EM_CODES webhook. Also covers E/M Coding with Ambient via CreateSession.artifacts and EM structured-data GETs. Do not invent non-OpenAPI paths.
suki-em-coding
Use when building Suki E/M Coding integrations: choose Ambient or standalone generation, seed coding context, retrieve Evaluation and Management codes, and map results into partner RCM or EHR handoff. Do not treat E/M Coding as a fifth clinical workflow.
suki-form-filling-api
Use for direct Partner Form filling APIs (not SDKs): authenticate, create a Form filling session, seed Medical form template IDs and/or partner dynamic schemas in context, stream visit audio on /ws/stream with Ambient-style framing, end the session, and retrieve structured-data. Do not use for Form filling SDK or Web SDK embeds.
suki-form-filling-sdk
Use when embedding hosted Suki Form filling with @suki-sdk/form-filling or @suki-sdk/form-filling-react: SukiAuthManager, FormFillingClient, preferred forms (static/dynamic/mixed), form_template_ids, correlation_id, fixed-height container, and onSubmit structured results. Prefer this over raw Form filling APIs for hosted UI. Web SDK v3.2.0+ includes Form filling clients; dynamic forms need Web SDK v3.3.1+ or Form filling SDK v0.1.0-beta.3+.
suki-form-filling
Use when building Suki Form filling integrations with the Form filling APIs or SDK: authenticate, create a Form filling session, provide Medical form template context, stream visit audio, end the session, and retrieve structured medical form output.
suki-headless-web-sdk
Use when building custom Ambient UI with the Headless Web SDK (@suki-sdk/platform-react): PlatformClient, PlatformClientProvider, useAuth, useAmbient create (encounterId required; emrEncounterId for interoperability v0.3.0+), noteId, useAmbientSession for start/pause/resume/submit/cancelRemote/endRemote, onSessionTerminatedByPeer, useGetEncounterInfo, sessionStatus vs local recording phase, offline sessions, setSessionContext / updateSessionContext (including Embedded Forms on sections[].precharted_content), and structured-data / section-structured-data hooks. Do not mix with DictationClient or headed SukiAssistant.
suki-mobile-sdk
Use when integrating Ambient or Form filling on native iOS with SukiAmbientCore: initialize before create, createSession with sessionType ambient or formFilling, setSessionContext / setFormFillingContext, record with start/pause/resume/end, and retrieve note content or form structured data. Do not paste Ambient API /ws/stream framing into Swift.
suki-patient-summary-api
Use for direct Partner Patient Summary APIs (not Web SDK embeds): authenticate, ingest FHIR R4 into the Clinical Knowledge Graph (CKG), generate summaries for encounters or provider schedules, poll asynchronous jobs, and retrieve full or pre-visit summaries. Do not use for Web SDK Patient Summary UI.
suki-patient-summary
Use when building Suki Patient Summary integrations: ingest FHIR R4 data into the Clinical Knowledge Graph (CKG), authenticate Patient Summary APIs, generate summaries for scheduled appointments or individual encounters, monitor asynchronous generation jobs, and retrieve completed full or pre-visit summaries.
suki-web-sdk
Use when embedding the Headed Web SDK with @suki-sdk/js or @suki-sdk/react and @suki-sdk/core: SukiAuthManager, initialize/init, mount or SukiAssistant, controlled Ambient (startAmbient, activeAmbientId), encounter context, ambientOptions nesting, Medication orders (LOINC 52471-0), built-in Dictation and Form filling, minimized layout, interoperability, and Patient Summary on the patient profile (v3.3.0+).
suki-webhooks
Use when implementing Suki partner webhooks for Ambient, Form filling, standalone E/M Coding, and CKG FHIR ingestion notifications, including callback configuration, HMAC signature verification, payload handling, and delivery retries.
suki-platform
Use when choosing among Suki Ambient, Form filling, Dictation, Patient Summary, audio streaming, webhooks, SDKs, or Partner APIs, or when the product path is unclear. After the product is known, fetch that product skill instead of relying on this router alone.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Suki β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing β they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications streaming
- Agent card
- https://developer.suki.ai/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.