komaa.com valid

StandIn

Put your AI agent into a Microsoft Teams call. One SDK in Python and TypeScript, framework plugins, and runnable examples.

For agents: StandIn SDK (Python and TypeScript) to put an AI agent into Microsoft Teams calls, with quickstart, Azure bot setup and connection docs.

ai agent voicemicrosoft teamspython sdktypescript sdkazure bot

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T23:33:57.006Z. Cached copy · Source on komaa.com

# StandIn

> Put your AI agent into a Microsoft Teams call. One SDK in Python and TypeScript, framework plugins, and runnable examples.

- [StandIn](https://docs.komaa.com/index.md): Put your AI agent into a Microsoft Teams call. One SDK in Python and TypeScript, framework plugins, and runnable examples.
- [Quickstart](https://docs.komaa.com/quickstart.md): Answer a real Microsoft Teams call with the StandIn SDK: install the package, expose one port, register the agent voice URL, and hear yourself back.
- [Microsoft Teams setup overview](https://docs.komaa.com/teams/overview.md): What you need to connect your agent to Microsoft Teams: an Azure bot identity, the StandIn app package, and a one-time upload to Microsoft Teams.
- [Connection modes](https://docs.komaa.com/teams/connection-modes.md): Two ways to put your agent in Microsoft Teams: the StandIn AI Teammate app from the Microsoft Teams Store, or your own Azure bot.
- [Create the Azure bot](https://docs.komaa.com/teams/azure-bot.md): Register a Microsoft Entra app, create the Azure Bot resource, enable Microsoft Teams calling, and grant the Graph permissions StandIn needs.
- [Get the Microsoft Teams app package](https://docs.komaa.com/teams/app-package.md): Download the generated Microsoft Teams app package (manifest zip) from StandIn, or build it yourself from the example manifest.
- [Upload to Microsoft Teams and go live](https://docs.komaa.com/teams/publish.md): Upload the app package as a custom app or publish it to your organization, register your agent in StandIn, and place the first call.
- [Architecture](https://docs.komaa.com/concepts/architecture.md): What the StandIn service owns, what the SDK owns, and what your plugin owns: the handler seam, the session, the two lanes, and the wire facts.
- [Dialogue modes](https://docs.komaa.com/concepts/modes.md): Realtime speech-to-speech or a streaming STT, agent, TTS pipeline: how much of each the SDK carries, how to choose, and which mode every shipped plugin drives.
- [What the SDK gives you](https://docs.komaa.com/concepts/features.md): The capabilities the StandIn SDK actually exposes: the call seam, audio, vision and the avatar, recap, outbound calling, the chat lane, signatures and capacity, and what it deliberately does not do.
- [Tiers and what each gives you](https://docs.komaa.com/tiers.md): The two ways to connect an agent to StandIn: a Free identity on your own Azure bot, and the StandIn AI Teammate app. How to tell which one you are on, what each gives you, and what each costs you.
- [Expose your agent](https://docs.komaa.com/expose.md): StandIn dials your worker from the internet. The one path to publish, the mount commands, and the probes that tell a real fault from a fake one.
- [Troubleshooting](https://docs.komaa.com/troubleshooting.md): The failures a StandIn worker actually produces: a silent HMAC mismatch, an unreachable worker, a probe that lies, a bot that answers every turn of a meeting, an agent that answers itself,
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=komaa.com · GET /v1/domain/komaa.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for komaa.com:
1. POST https://agentwebmap.com/v1/sites/komaa.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://komaa.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/komaa.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/komaa.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.