ReadMe scores $9M Series A to help firms customize API docs

Published August 28, 2019

Software APIs help different tools communicate with one another, let developers access essential services without having to code it themselves and are critical components for driving a platform-driven strategy. Yet they require solid documentation to help make the best use of them. ReadMe, a startup that helps companies customize their API documentation, announced a $9 million Series A today led by Accel with help from Y Combinator. The company was part of the Y Combinator Winter 2015 cohort.

Prior to today’s funding announcement, the company had taken just a $1.2 million seed round in 2014. Today, it reports 3,000 paying customers and that it has been profitable for the last several years, an unusual position for a startup. In spite of this success, co-founder and CEO Gregory Koberger said as the company has taken on larger customers, they have more sophisticated requirements, and that prompted them to take this round of funding.

In addition, it has expanded the platform to use a company’s API logs to help create more dynamic documentation and improve customer support kinds of scenarios. But by taking on data from other companies, it needs to make sure the data is secure, and today’s funding will help in that regard.

“We’re going to still build the company traditionally by hiring more engineers, more support people, more designers, the obvious stuff, but the main impetus for doing this was that we started working with bigger companies with more secure data. So a lot of the money is going to help make sure that we handle that right,” Koberger explained.

Image: ReadMe

He says this ability to make use of the API logs has opened up all kinds of possibilities for the company, as the data provides a valuable window into how people use the APIs. “It’s amazing how much you get by just actually seeing what the server sees. When people are having problems with an API, they can debug it themselves because they can actually see the problems, the support team can see it as well,” Koberger said.

Accel’s Dan Levine, whose firm is leading the investment, believes that having good documentation is the difference between making and breaking an API. “APIs don’t just create technical integration, they create ecosystems around core services and underpin corporate partnerships that generate billions of dollars. ReadMe is as much a strategy as it is a service for businesses. Providing clean, interactive, data-driven API documentation to make developers love working with you can be the difference between 100 partnerships or 1,000 partnerships,” Levine said.

ReadMe was founded in 2014. It has 22 employees in their San Francisco office, a number that should increase with today’s funding.

Smartcar accuses $50M-funded rival Otonomo of API plagiarism

Published April 23, 2019

Ruthless copying is common in tech. Just ask Snapchat. However, it’s typically more conceptual than literal. But car API startup Smartcar claims that its competitor Otonomo copy-and-pasted Smartcar’s API documentation, allegedly plagiarizing it extensively to the point of including the original’s typos and randomly generated strings of code. It’s published a series of side-by-side screenshots detailing the supposed theft of its intellectual property.

Smartcar CEO Sahas Katta says “We do have evidence of several of their employees systemically using our product with behavior indicating they wanted to copy our product in both form and function.” Now a spokesperson for the startup tells me “We’ve filed a cease-and-desist letter, delivered to Otonomo this morning, that contains documented aspects of different breaches and violations.”

The accusations are troubling given Otonomo is not some inconsequential upstart. The Israel-based company has raised over $50 million since its founding in 2015, and its investors include auto parts giant Aptiv (formerly Delphi) and prestigious VC firm Bessemer Ventures Partners. Otonomo CMO Lisa Joy provided this statement in response to the allegations, noting it will investigate but is confident it acted with integrity:

Otonomo prides itself on providing a completely unique offering backed by our own intellectual property and patents. We take Smartcar’s questions seriously and are conducting an investigation, but we remain confident that our rigorous standards of integrity remain uncompromised. If our investigation reveals any issues, we will immediately take the necessary steps to address them.

Both startups are trying to build an API layer that connects data from cars with app developers so they can build products that can locate, unlock, or harness data from vehicles. The 20-person Mountain View-based Smartcar has raised $12 million from Andreessen Horowitz and NEA. A major deciding factor in who’ll win this market is which platform offers the best documentation that makes it easiest for developers to integrate the APIs.

“A few days ago, we came across Otonomo’s publicly available API documentation. As we read through it, we quickly realized that something was off. It looked familiar. Oddly familiar. That’s because we wrote it” Smartcar explains in its blog post. “We didn’t just find a few vague similarities to Smartcar’s documentation. Otonomo’s docs are a systematically written rip-off of ours – from the overall structure, right down to code samples and even typos.”

The screenshot above comparing API documentation from Smartcar on the left and Otonomo on the right appears to show Otonomo used nearly identical formatting and the exact same randomly generated sample identifier (highlighted) as Smartcar. Further examples flag seemingly identical code strings and snippets.

Smartcar founder and CEO Sahas Katta

Otonomo has pulled down their docs.otonomo.io documentation website, but TechCrunch has reviewed an Archive.org Wayback Machine showing this Otonomo site as of April 5, 2019 featured sections that are identical to the documentation Smartcar published in August 2018. That includes Smartcar’s typo “it will returned here”, and its randomly generated sample code placeholder “”4a1b01e5-0497-417c-a30e-6df6ba33ba46” which both appear in the Wayback Machine copy of Otonomo’s docs. The typo was fixed in this version of Otonomo’s docs that’s still publicly available, but that code string remains.

“It would be a one in a quintillion chance of them happening to land on the same randomly generated string” Smartcar’s Katta tells TechCrunch.

Yet curiously, Otonomo’s CMO told TechCrunch that “The materials that [Smartcar] put on their post are all publicly accessible documentation, It’s all public domain content.” But that’s not true, Katta argues, given the definition of ‘public domain’ is content belonging to the public that’s uncopyrightable. “I would sure hope not, considering . . . we have proper copyright notices at the bottom. Our product is our intellectual property. Just like Twilio’s API documentation or Stripe’s, it is published and publicly available — and it is proprietary.”

Otonomo’s Lisa Joy noted that her startup is currently fundraising for its Series C, which reportedly already includes $10 million from South Korean energy and telecom holdings giant SK. “We’re in the middle of raising a round right now. That round is not done” she told me. But if Otonomo gets a reputation for allegedly copying its API docs, that could hurt its standing with developers and potentially endanger that funding round.