Pawgo.fr's answer

No one else does what PawGo does. Here's why: pet travel rules are scattered across hundreds of airline PDFs, government websites, and vet forums — all in different formats, different languages, and constantly changing. Today people spend hours or days piecing together info from 10+ sources, and still miss things. One wrong document = denied boarding or quarantine.

What exists today:

Government websites (raw regulation text, hard to parse) Pet relocation companies ($500-3,000, manual process, takes weeks) Blog posts (generic, outdated within months) Facebook groups (anecdotal, contradictory advice) What PawGo does differently:

Automated, not manual. An AI agent crawls and verifies the actual sources 24/7. No human copy-pasting from PDFs. Personalized, not generic. Your breed + your airline + your destination = your exact checklist. A French Bulldog on Air France to Japan gets a completely different plan than a Labrador on Delta to Spain. Deadline-aware. It calculates backwards from your departure: "book vet appointment by May 3, get USDA endorsement by May 7, freeze water bowl May 9." Not just "get a health certificate." Cross-referenced. It checks airline rules AND country rules AND breed restrictions simultaneously. No other tool connects all three. Free. Pet relocation services charge hundreds. PawGo is free, no signup.

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.

Pawgo.fr's answer

I rescued stray dogs in Morocco. Not one — several, over multiple trips. Each time I had to figure out how to get them on a plane to Paris, and each time it was a mess.

Morocco is a high-risk rabies country, which means the rules are brutal: titer tests with 3-month waiting periods, specific vaccination sequences, health certificates that expire in 10 days, government endorsements that take a week. Every airline had different carrier rules. Every vet gave me different advice. I spent days on the phone with Air France, hours on Moroccan government websites in Arabic, and made multiple trips to the DDPP office for document stamps.

I got it wrong more than once. Missed a vaccination deadline by two days — had to rebook the flight and wait another month. Showed up at CDG with a carrier that was 2cm too tall — almost didn't board. Had a health certificate rejected because the microchip number was written in the wrong field.

After the third rescue, I realized I was rebuilding the same research from scratch every time. And if it was this hard for me — someone who'd already done it — imagine a first-time pet traveler trying to figure this out.

So I built PawGo. Everything I learned the hard way, automated. The tool I wish I'd had the first time I walked into Casablanca airport with a scared dog in a crate and a folder full of papers, hoping I hadn't missed anything.

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.

Pawgo.fr's answer

Stack: Python, FastAPI, Claude API, PostgreSQL, Railway, Bubble, Google Search Console API.

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.

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.

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.