The request "vte" is ambiguous: it names no product, operation, or platform. The candidate products span unrelated categories (databases, search, cloud, AI models, payments), so I cannot identify which tool is wanted without more context.
A question back: What do you want to do with "vte" (for example: a specific product name, a task like text-to-speech or virtual try-on, or a tool for a particular platform)?
For agents: the 10 actions behind this answer
vitest · vitest verified and signed
Vitest API and config reference (Jest-compatible) — mocking with vi.*, spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering. Use for Vitest API and configuration questions anywhere in the monorepo; for Studio-specific test strategy and component-test setup, start with
video_vto · adk-recipes found in code, not yet checked
Generate virtual try-on video of a person wearing garments or glasses.
migrate-to-vinext · migrate-to-vinext verified and signed
Migrates Next.js projects to vinext (Vite-based Next.js reimplementation). Load when asked to migrate, convert, or switch from Next.js to vinext. Handles compatibility scanning, package replacement, Vite config generation, ESM conversion, and deployment setup (Cloudflare Workers natively, other plat
gtm-ai-gtm · gtm-ai-gtm verified and signed
Go-to-market strategy for AI products. Use when positioning AI products, handling "who is responsible when it breaks" objections, pricing variable-cost AI, choosing between copilot/agent/teammate framing, or selling autonomous tools into enterprises.
type · typing verified and signed
speech-to-text · Parakeet CTC 0.6B Vietnames English ASR verified and signed
Task: Speech to Text
learning · peft verified and signed
stripe · stripe verified and signed
python · fastcore verified and signed
gitea · gitea verified and signed
Interact with Gitea using the `tea` CLI. Use `tea issue`, `tea pr`, `tea actions`, and `tea api` for issues, PRs, Actions, and advanced queries.
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.