TranscriptFetch's answer

Most short-form video has no caption track to download. TikTok’s auto-captions are opt-in per upload, Instagram never publishes a downloadable track, and many captions on both are burned into the video frames where no parser can read them. TranscriptFetch transcribes the audio when no caption track exists, on the same endpoint, with the same response shape. Your code never branches on which method produced the text. It also covers YouTube, TikTok, Instagram, X and Facebook plus any web page as clean Markdown, so a pipeline spanning several sources is one integration rather than five.

WYA Friends's answer:

WYA turns the messy back-and-forth of group chats into a single shared link. You create a "WYA Session" – a title, time, optional place and decide who's invited, literally in seconds. Then additionally you can share it via WhatsApp or iMessage or where ever. Friends tap the link, see the details and can even RSVP without being forced to download anything. If they have the app nevertheless they can easily chat, send polls or share pictures within each session.

TranscriptFetch's answer

Three reasons. Coverage: one API key and one response shape across five video platforms and the open web, instead of stitching together a library per platform. Reliability: requests run through rotating infrastructure, so code that works locally keeps working from a server, which is where most open-source approaches break. Billing that matches reality: one credit per successful response, with failed, blocked and empty results never charged. That last point matters on short-form video, where a meaningful share of any batch is music with no speech in it. There is also an MCP server, so AI agents can fetch transcripts as a tool without a custom integration.

WYA Friends's answer:

Most coordination tools make you do more work: scheduling polls, formal event pages, or calendar-booking flows. WYA is built for the opposite: Spontaneous, low-effort meetups with friends you want to see. It's faster to create, asks nothing of your friends except a tap and keeps the plan in one clear place instead of buried in a chat thread. It doesn't try to replace chat apps; it removes the friction inside it.

TranscriptFetch's answer

Developers and technical teams building on video and web content. The common cases are RAG and retrieval pipelines that need video as text, AI agents that need to read a link mid-conversation, content teams repurposing short-form video at scale, and media monitoring and research tools. It is an API first, so the buyer is usually the person writing the integration rather than an end user. The free browser tools exist for one-off transcripts and for evaluating output quality before writing any code.

WYA Friends's answer:

WYA Friends is for socially active people who struggle to turn "we should catch up" into an actual plan. Friend groups, crews and community organizers who meet up often. The broader audience is anyone who'd rather send one link than herd a group chat toward a decision.

TranscriptFetch's answer

It started with discovering there is no good way to get the text of a video. YouTube’s official Data API will confirm a caption track exists and then refuse to hand it over, because captions.download requires the video owner’s OAuth token. The popular open-source libraries work until you deploy them, at which point platforms start refusing datacenter IPs. And YouTube is the easy case: TikTok and Instagram publish no caption file at all. Every workaround solved one platform, worked locally, and broke in production. TranscriptFetch is the version that handles the failure cases as first-class behaviour rather than edge cases.

WYA Friends's answer:

WYA started from a simple frustration: The friends we most want to see are the ones we keep saying "we should catch up" to and in the end never do. Group chats are where plans go to die, lost in back-and-forth that never lands on a time and place. WYA was built in Berlin to fix exactly that, make proposing a meetup so fast and low-friction that spontaneous plans actually happen. Less planning, more seeing each other.

TranscriptFetch's answer

Next.js with TypeScript and Tailwind on the front end and API layer, Clerk for auth with SHA-256 hashed API keys, Neon Postgres with Drizzle ORM, Redis for caching, and Stripe for billing. The extraction layer is a Python and FastAPI service. Speech-to-text uses Whisper-class models. The MCP server is published in the official Model Context Protocol registry with a DNS-verified namespace.

WYA Friends's answer:

WYA Friends is built with Flutter (iOS) on a Firebase backend. Firebase Auth, Firestore, Cloud Functions, Cloud Storage, and Cloud Messaging (FCM) for push notifications. CI/CD runs through Xcode Cloud. The web landing pages are built with React, TypeScript and Vite.

WYA Friends's answer:

WYA Friends is a free consumer app, not an enterprise product, it's used by friend groups and early community organizers in Berlin rather than corporate customers as of now. Nevertheless we plan to expand the use case of WYA for professionals in the future.