The first sign that something had shifted in developer tools arrived quietly, without much fanfare. An AI agent successfully called an API. A human developer copy-pasted a code snippet and it actually worked. No Stack Overflow dive. No Slack plea to the founders.
That moment—mundane as it sounds—is increasingly where revenue starts.
Manicule, a five-person team barely six months into existence, has built a business around this premise. The Y Combinator-backed startup operates as a documentation studio for other developer tools companies, promising to ship complete technical content in roughly two weeks. The pitch is straightforward: your docs should work for humans and for the autonomous agents now crawling through API references like impatient junior developers.
The early traction suggests they're onto something, even if the model raises questions about what exactly scales. According to the company's Y Combinator profile, Manicule hit $58,000 in monthly recurring revenue with 100% month-over-month growth over the past three months. The customer roster reads like a cross-section of the YC developer tooling ecosystem: Greptile, Reducto, Supermemory, Skyvern, Rootly, Promptlayer.
Not bad for a company whose founders are both 18 years old.
How It Actually Works
Manicule doesn't offer a self-serve platform. There's no dashboard where you plug in your API specs and get auto-generated docs. Instead, they function more like a boutique agency with proprietary tooling—taking full ownership of technical content from documentation to developer blogs, cookbooks, video tutorials, even distribution strategy across social channels and generative search engines.
Most projects ship in about 15 days, then transition to ongoing maintenance. It's a tight feedback loop, perhaps more than the founders expected when they started.
The workflow itself is a hybrid. AI agents handle the mechanical verification work: auditing existing docs, testing whether code snippets actually compile and run, pinging endpoints to make sure they return the promised responses. Humans handle information architecture, messaging, quality control. The division of labor makes sense—agents excel at the tedious stuff that tends to rot when a startup's API evolves faster than its documentation team.
One data point from Supermemory, a customer, illustrates the impact: a 30% increase in answer success rate, multiple enterprise deals closed in part because of clearer documentation, and a 23-day timeline from kickoff to launch. The Supermemory documentation also went "viral on Twitter," though quantifying viral is always slippery. Still, a quote attributed to Michael Chomsky from October 2025 on Manicule's website suggests the attention was meaningful, even if that predates the company's formal launch.
The Agent-Optimized Bet
The company leans heavily into agent-readable documentation. Chrome for Developers described llms.txt—a machine-readable documentation index—as an "emerging convention" for large language models and agents in early May 2026. Several Manicule customers, including Greptile and Rootly, have already implemented these indices in their documentation.
Timing matters here. Forrester's "The State of Agentic AI, 2026" report, published in late May, argued that agent viability has arrived and platforms are reshaping around autonomous workflows. TechRadar Pro noted that "the moment an AI agent returns 200 OK" is becoming a conversion event for API-first companies.
Manicule's launch materials claimed customers saw roughly 37% fewer support tickets and millions of impressions across AI search and social channels. The company also claims that better docs influenced over $100,000 in enterprise deals—though documentation ROI is notoriously difficult to attribute cleanly. Did the improved docs close the deal, or were they simply table stakes?
Why This Wedge Exists
The economics of developer relations have gotten thorny. Job postings for senior Developer Experience roles at companies like Sentry, Anthropic, and OpenAI show compensation bands ranging from $220,000 to $320,000, according to listings from DevRelJobs.com in late May 2026. That's expensive talent, especially for early-stage companies still figuring out product-market fit and burn rate.
Manicule's founders—CEO Naman Bansal and Shreyans Jain—are selling speed and ownership as the alternative. They're not competing with self-serve documentation platforms like Mintlify or ReadMe, which handle hosting and publishing infrastructure. Instead, they're competing with the choice to hire an internal DevRel team or engage a traditional content agency like Draft.dev.
The company raised $500,000 on a convertible note, according to CB Insights data from spring 2026. LinkedIn posts from the founders around that time referenced the funding as part of their Y Combinator Spring 2026 batch acceptance. They incorporated in California on May 20, 2026, per state registry data, and posted their official YC launch announcement shortly after. The timeline suggests they moved quickly—reportedly entering YC with $150,000 in annual recurring revenue already on the books, according to founder posts from around April.
A recent podcast interview on "Agentic Stories," posted May 30, revealed more about their internal tooling. Bansal described a two-week delivery cycle powered by a pipeline of sub-agents, including a GitHub app for codebase exploration and a separate context repository. The company appears to be building proprietary infrastructure to support what is, at its core, a high-touch service model.
The Scale Question
Whether documentation-as-a-service can reach venture-scale outcomes remains an open question. The customer list is impressive—multiple YC companies betting their developer experience on an outside team rather than building in-house. But the model is intentionally labor-intensive. Five people can only handle so many concurrent projects, even with agents doing the grunt work.
Manicule will need to prove it can maintain both quality and speed as it adds customers. Documentation is unforgiving. One outdated code sample, one broken API endpoint in a tutorial, and trust erodes fast. Developers are less forgiving than most user bases.
For now, Manicule has carved out a specific wedge: developer tools companies that need production-quality documentation shipped quickly, with an eye toward the agent-driven future of software distribution. It's a narrow focus.
Maybe that's exactly what works. In developer tooling, specificity often beats breadth. And if the company is right that documentation has become a conversion funnel—that the moment an agent or human successfully runs your code sample is where deals begin—then perhaps there's more room in this market than it first appears.
The founders, barely old enough to rent a car in most states, seem to be betting their early twenties on it.
