Skribby Q1 wrapped: meeting bot API and AI transcription updates
A recap of what Skribby shipped in Q1 for teams building with a meeting bot API, AI transcription workflows, and real-time voice products.
In the past few months, we focused on four things: expanding regional infrastructure, adding more transcription options, improving the platform itself, and broadening meeting platform support. If you're new here, Skribby is a meeting bot API for Zoom, Microsoft Teams, and Google Meet, built for teams shipping transcription, AI meeting assistants, and real-time voice features, with docs for REST API integrations and TypeScript SDK usage.
Infrastructure and regional expansion
One of the biggest updates this quarter was the launch of our Japan region.
With dedicated Tokyo infrastructure, customers in Asia can now run low-latency bots closer to their users. Besides the latency benefits, this region is also around 30% cheaper than alternatives, making it a strong option for teams that care about both performance and cost. For teams looking for a Japan meeting bot API setup, this gives you a region-local option with better latency and data residency alignment. If you need region-specific setup details, see our regions guide.
New transcription models
We also expanded the transcription models available on Skribby, giving developers more flexibility depending on whether speed, accuracy, or familiarity matters most. This is especially useful for teams building AI meeting products, voice agents, or transcription-heavy workflows. For the broader list of supported options and naming conventions, see the transcription models guide. If you're comparing options, our blog post on the best transcription model for meeting bots is also a useful starting point.
- Mistral Voxtral Mini 2 is now available as a realtime transcription option built for speed.
- AssemblyAI Universal-3 Pro was added as a premium model for use cases where transcription quality is the priority.
- ElevenLabs Scribe v2 is now available as an improved version of an already popular model.
Together, these additions make it easier to choose the right setup for different product and customer needs.
Platform improvements
On the platform side, we shipped several features designed to make Skribby easier to integrate into real production workflows.
Custom metadata on bots
You can now attach your own metadata to any bot, making it easier to track bots internally and match them to records in your own system.
Pricing API endpoint
We introduced a pricing API endpoint so customers can query pricing programmatically. This is especially useful for dynamic cost calculations inside your own product or internal tooling. For general pricing context, see our pricing page.
Webhook signing and security
We also added signature verification and secrets management for webhooks, so you can verify that incoming events genuinely came from Skribby. If you're implementing this now, our webhook security guide walks through the verification flow.
Expanded meeting platform support
We continued to improve support for webinar-specific flows and meeting platform coverage.
Zoom Webinar support
Support now includes registration handling, webinar chat, and the full disclaimer flow. If you're working with Zoom-specific chat behavior, our Zoom chat guide covers meetings vs. webinars and threading behavior.
Teams Webinar support
We added a direct-join flow with webinar-specific UI for Teams Webinar.
Zoom Chat threading
Threading metadata is now included in chat webhooks, making it easier to work with threaded Zoom conversations downstream. This pairs nicely with the existing Zoom chat documentation.
A small look at what’s next
While this update is mainly about what shipped in Q1, there are already a couple of things in progress.
We’re actively working on Zoho Meeting support, including join flow, authentication, chat, waiting rooms, and more. For teams exploring a future Zoho Meeting bot API workflow, this is one of the areas we’re actively investing in.
We’re also exploring more agentic features, with a focus on more interactive real-time bot behavior, live updates, talking bots, and other more dynamic AI experiences.
More to share on that soon.
Build with Skribby
If you’re looking for a meeting bot API and want to get started quickly, you can try Skribby for free.
No credit card is required, and every account includes 5 free hours to get started. You can also jump straight into our quickstart guide, browse the REST API docs, or use the TypeScript SDK.
If there’s a platform or feature you’re missing, let us know. We read every reply.
FAQ
What is a meeting bot API?
A meeting bot API lets developers send bots into platforms like Zoom, Microsoft Teams, and Google Meet to capture transcripts, recordings, chat messages, and other meeting data programmatically.
Which transcription models does Skribby support?
Skribby supports a growing set of transcription models for different needs, including realtime and post-meeting options. You can explore the broader model list in our transcription models guide.
Does Skribby support webinars?
Yes. Skribby supports webinar-related workflows, including Zoom Webinar support and Teams Webinar support, with continued improvements across platform-specific join flows and chat behavior.
Is Skribby working on a Zoho Meeting bot API?
We’re actively working on Zoho Meeting support. If you’re looking for a Zoho Meeting bot API for transcription, recordings, or meeting automation workflows, this is one of the areas on our roadmap.
Does Skribby offer a Japan meeting bot API region?
Yes. Skribby offers a Japan region for teams that need lower latency in Asia or stronger Japan-focused data residency alignment for their meeting bot API workflows.
Can I use Skribby for AI transcription workflows?
Yes. Skribby is built for teams creating AI transcription workflows, meeting assistants, voice products, and other applications that depend on real-time or post-meeting conversation data.
How do I get started with Skribby?
You can start with the quickstart guide, browse the REST API docs, or use the TypeScript SDK.