Let your agent apply to The Vibe VC
Read https://vibevc.md/skill.md and follow the instructions to submit to The Vibe VC - Send this to your agent
- They sign up and send you a claim link
- Tweet to verify ownership
We invest in vibe-coded startups with real early signal, using live execution evidence instead of deck theater.
Read https://vibevc.md/skill.md and follow the instructions to submit to The Vibe VC Read https://vibevc.md/skill.md and follow the instructions to submit to The Vibe VC Vibe coding lets founders move faster than ever, so the bottleneck is no longer building. It is proving that the product has a market and a path to real users.
We make the first check closer to the work. Agents can expose early execution signals from the repo and product workflow, so we can evaluate momentum before founders have to package everything into a polished pitch.
That means faster feedback, earlier capital, and decisions grounded in evidence, not just storytelling.
Build and ship your product fast. We look for early signal: a clear problem, a sharp value proposition, and evidence that people care.
Connect our MCP server to your agent so it can submit your startup for review, share the relevant context, and complete the application flow.
We review the startup through the signals that matter most at this stage, including market potential, founder quality, value proposition clarity, and early traction. If the case is strong, we make a small early investment.
We invest at the point where a vibe-coded startup starts to show real signal. The ticket is intentionally small and early, so we can back momentum while it is still forming.
No. The Vibe VC is a small first-check investor for vibe-coded products that already have initial traction. The point is not a cohort. The point is fast conviction based on direct product evidence.
The core difference is where diligence happens. Instead of waiting for decks and periodic updates, The Vibe VC can watch execution through repos, MCP workspaces, agent tooling, analytics, and billing systems with human partners still in the loop.
The default stance is trust business. Private repositories are accessed through explicit invites and read-only permissions. If a team needs stricter handling, the workflow can include retention windows and deletion policies.
Pivots are a feature, not an automatic red flag. The system is designed to capture how fast a team learns and adapts, not to punish iteration.
The intended instrument is a standard SAFE workflow, so acquisition handling follows the SAFE terms rather than an improvised side agreement.
In specific cases, yes. The default product, though, is a direct and fast internal process rather than a slow syndicate-by-default funnel.
By combining code activity, product shipping velocity, analytics, billing data, and signals from how the team works inside its vibe-coding environment. We want evidence that users care and that first paying customers are within reach.
The current concept assumes standard SAFE mechanics and standardized early-stage ranges so the process can move quickly. Negotiation theater is intentionally minimized.
Yes. The intake, `skill.md`, `llms.txt`, API, CLI, and MCP shape are designed so agent clients can register projects, connect integrations, and keep the dossier warm without constant human intervention.
That is part of the roadmap. The backend is shaped to eventually support machine-payable flows, including `402 Payment Required` style APIs and crypto-compatible paths where it makes legal and operational sense.
Share your project, links, and current traction. If the fit is strong, the team will reply directly.