Inkeep’s cover photo
Inkeep

Inkeep

Software Development

San Francisco, California 3,621 followers

AI Agents for Customer Operations.

About us

Inkeep helps companies ship AI Agents for customer experience, GTM, and operations teams. Inkeep Agents are deployed at scale today with leading companies like Anthropic, Midjourney, Clay, and PostHog to help with everything from customer support to in-product copilots to sales. Our Agent Engineering team works closely with Enterprises and high-growth teams to deliver on reliable agents quickly, but we also offer a full open source platform so your teams can own and manage agents in the long run. Accessibility is our goal: agents can be edited and managed by both engineers and business teams, all in a single platform. Business teams get an intuitive drag-and-drop visual builder while engineers get developer SDK with type safety, CI/CD, version control, and all the code-based tools they expect. Platform highlights: - A No-Code Agent Builder and Developer Framework with full 2-way sync - Unified search and RAG for knowledge bases, docs, and company data - MCPs and integrations with your APIs and software - Intelligent insights and monitoring over how Agents perform Backed by Khosla Ventures, Y-Combinator, Great Point Ventures, and other leading investors.

Website
https://go.inkeep.com/INK-LN-PROF
Industry
Software Development
Company size
11-50 employees
Headquarters
San Francisco, California
Type
Privately Held
Founded
2023
Specialties
generativeai, llms, search, neuralsearch, rag, support, retrieval, ai, ml, devtools, chatbot, genai, aichat, productmanagement, analytics, deflection, devex, customer engagement, self-service, customer support, customer service, customer engagement, customer success, technical support, support copilot, cx, customer engagement, customer experience, customer support, aiteammates, aiagents, agents, agent workforce, ai agents, ai assistants, ai teammates, unified search, enterprise search, workflows, agent workflows, business automation, multi-agent, no-code, agent builder, agent engineering, ai agents, gtm agents, sales agents, marketing agents, in-product agents, in-product copilots, operations, automations, low-code, agent framework, workflow builder, visual builder, conversational agents, chat assistant, and ai assistant

Locations

Employees at Inkeep

Updates

  • View organization page for Inkeep

    3,621 followers

    We’re launching something special. Introducing OpenKnowledge, a beautiful macOS app designed to be the best experience for authoring AI-native knowledge bases. For personal and team use, available as a macOS app.

    Today, we’re announcing OpenKnowledge, the best markdown doc editor for agents + humans. Like many teams, we’ve found markdown files are the best agent-friendly format for all text-based content: skills, specs, docs, blogs, everything. We’ve moved all of our internal KBs, blog system, product docs, and software development artifacts to use markdown. It’s so powerful to have a centralized, normalized way for agents to help us create and maintain content, but it can also be a painful experience. We faced the same problem we’re hearing from other teams: markdown files are a pain to actually author, edit, and share. So we set out to build a beautiful editor with the ergonomics that feel as good as Google Docs and Notion, while developing it from the ground up to be markdown-first and work natively with Claude, Codex, and other agents. We built it as a macOS app that runs privately and locally on your device: no data touches our servers. All open source as well. Some highlights: 💻 macOS app and web UI with built-in integrations to popular AI agents. 🔗 1-click share and auto-sync for team collaboration backed by Git ⚡ Agentic search so agents can easily find the right content. 🧠 MCPs and skills to create “LLM wikis” and knowledge bases. Super proud of the team for the ship, and just marking the start.

  • View organization page for Inkeep

    3,621 followers

    The fastest way to make your AI agents smarter isn't a better model. It's better docs. Customer-facing assistants, internal copilots, sales research agents, support deflection bots. Every one of them is only as smart as the knowledge base they're reading from. Which means every outdated article compounds. It's not one stale doc anymore. It's: → A customer-facing AI quoting last quarter's pricing as fact → An engineering copilot suggesting an API endpoint that was deprecated two releases ago → A sales rep's research agent missing the new feature that would have answered the prospect's biggest objection → A customer success agent prepping for a QBR with talking points from before the platform overhaul Same gap, multiplied across every agent that touches the KB. The bigger failure isn't the agent saying "I don't know." It's the agent giving an outdated answer with full confidence. The customer makes the wrong decision. The engineer ships against the wrong API. The prospect walks before anyone realizes the docs were wrong. By the time the gap surfaces, the damage is already downstream. The fix isn't a bigger model or a better retriever. It's a feedback loop between what your team actually knows and what your docs actually say. That's what we built Inkeep's Content Writer for. Resolved support tickets, GitHub PRs, and ad-hoc Slack messages from your team turn into doc drafts automatically. Every one queues for a human to review and approve. Your docs stay current. Your agents stay accurate. The rest of the business stops paying the tax. Try the interactive demo → https://lnkd.in/gRetdWXf

  • View organization page for Inkeep

    3,621 followers

    Your docs are always running behind product. And your AI assistant pays the price. Every support team I talk to has the same problem. Edge cases get answered in tickets and never make it back to the docs. Product ships faster than the changelog can keep up. Tribal knowledge stays trapped in Slack threads. An AI assistant grounded in your docs can only answer what's actually been written down; so the gap between what your team knows and what your assistant knows keeps widening. We just shipped Inkeep's Content Writer to close that loop. It works three ways: → Watches resolved support tickets and drafts updates when reps answered something that isn't yet in the docs → Watches GitHub PRs and flags articles that need to change when the product changes → Can be invoked directly in Slack: "we're shipping X next week, what articles need updating?" Every draft goes to a human for review and approval before anything publishes. The Content Writer does the audit and the first pass; your writers do what writers are actually good at: judgment. The outcome is the closed loop that's supposed to exist between support and docs, finally running on its own. Your docs stay current with what's actually shipping, and your Inkeep AI assistant gets meaningfully smarter every week, without anyone having to manage it. We're running 1-month pilots right now. Comment or DM if you'd like to see it on your own knowledge base. Watch the demo → https://lnkd.in/gCfY2BSH

    How Inkeep Updates Documentation Automatically

    How Inkeep Updates Documentation Automatically

    https://www.loom.com

  • View organization page for Inkeep

    3,621 followers

    Missed our latest webinar with Composio? We walked through how to give AI agents access to 15,000+ tools using Inkeep + Composio MCP servers — without building integrations from scratch. ⚡ Live demos connecting agents to Slack, GitHub, and Gmail 🧠 Best practices for production-ready agent integrations Watch the recording 👇 https://lnkd.in/g8KSiXd2

  • Inkeep reposted this

    We signed our first real office in 4 hours. 7 months ago, we at Inkeep were in a 'co-working' space: But the reality was: - Sales teams whispering on prospect calls. - 2 Zoom calls happening two feet apart. - Constant anxiety of eavesdroppers listening to our calls We’d outgrown our co-working with startups. But we weren’t ready for a multi-year lease either. What we needed was weirdly specific: • Flexible terms • Quiet rooms to actually think • Transit access we’d use • And yes… an ocean view to survive early-stage chaos We started talking to commercial brokers. We told JLL straight up: “We’re not ready for a big commercial lease.” This is where most firms would lose interest. Instead, they leaned in. They’ve built deep relationships with WeWork and other coworking operators. Their thesis is simple: Help the startup now, then earn the relationship later. Will Cassriel from JLL packed a full day of tours into one afternoon. Jonathan Smith (my Chief of Staff) flew out, and we walked every serious option. By sunset, we had our pick. But the real value wasn’t the tour. - They negotiated on our behalf. - Explained contract language we’d never seen. - And recently helped us extend our WeWork agreement so we could buy more time before making a bigger bet. For any founder navigating office decisions, I'd recommend choosing partners who optimize for the relationship, not the transaction. You can feel the difference immediately.

    • No alternative text description for this image
    • No alternative text description for this image
    • No alternative text description for this image
  • View organization page for Inkeep

    3,621 followers

    🚨 Happening this Thursday If you’re building AI agents that need to connect to real-world tools- this is for you. This Thursday, we’re going live with Inkeep + Composio to show how you can give AI agents access to 10,000+ tools without maintaining brittle, one-off connections. 🗓 Feb 26 ⏰ 10:00 AM PST 💬 RSVP in the comments What you’ll learn: • How Inkeep’s AI agent framework handles tool use and agentic workflows • Why integrations are critical for production-grade AI agents • How Composio’s MCP servers unlock 10,000+ tools out of the box • Live demo: connecting agents to Slack, GitHub, and Gmail • Best practices for auth, testing, and deploying agent integrations in production Speakers: 🎤 Omar Gonzalez — Founding Engineer, Inkeep 🎤 Jayesh Sharma — AI Engineer, Composio 🎤 Gaurav Varma — DevEx Engineer, Inkeep (Moderator) If you're serious about shipping real-world agents- don’t miss this. 👇 RSVP in the comments

    • No alternative text description for this image
  • View organization page for Inkeep

    3,621 followers

    🌟 Excited to see Descope's Docs MCP Server live! AI-powered IDEs are quickly becoming the default way developers build. Making product knowledge directly accessible inside those workflows is a big step forward, which is why we built an MCP of our own to help you 'vibe code' agents using our agents SDK (link in the comments). We’re proud that Inkeep is powering key under-the-hood components of Descope's MCP server with semantic search and RAG. Congrats to the Descope team on the launch 👏

    View organization page for Descope

    13,631 followers

    🚀 Introducing the Descope Docs MCP Server If you’re using AI-powered IDEs (who isn’t?), you now have an easy way to add auth to your apps and reference Descope product knowledge. Our Docs MCP Server is a hosted MCP server that gives AI agents and MCP-compatible tools direct, structured access to Descope’s product knowledge right where you already work. ✅ Troubleshoot errors and misconfigurations  ✅ Answer architectural and design questions ✅ Get direct docs excerpts and supporting references ✅ Tell your AI coding assistant to add Descope auth, widgets, authorization, and more to your app Links to get started are in the comments 👇 P.S. Thank you to Inkeep for powering key under-the-hood components of this MCP server with semantic search and RAG!

  • View organization page for Inkeep

    3,621 followers

    We think "Agent Engineer" is becoming a real role. After hundreds of hours building AI agents, we've condensed what we've learned into a new guide: • How to structure prompts that actually work • Troubleshooting when agents fail • Coordinating multiple specialists Not theory. Battle-tested techniques. Link in the comments below.

    • No alternative text description for this image
  • Inkeep reposted this

    Want a sense of what Heads of AI are thinking today? Consolidation. A pattern we see over and over is that when AI assistants first rolled out around the GPT-3.5 and GPT-4 wave, teams saw quick wins that felt transformational at the time. Those wins were real, but they were narrow, tied to specific domains or workflows, and rarely designed to generalize beyond the exact problem they were bought for. As teams tried to extend those wins to adjacent functions, the answer was almost always another tool, another vendor, another contract. Over time, this created a patchwork where context lived in silos, AI could not reason end-to-end, and humans quietly became the glue doing the real work by stitching systems together manually. The irony is that the more “AI” teams adopted, the more operational drag they introduced, and the less leverage they actually gained. Fast forward two years and many Heads of AI are now managing bloated stacks with upcoming renewals, uneven technical depth, and very little real autonomy in the system. When VPs come to agentic platforms like Inkeep, what actually drives adoption is not novelty, but the ability to connect tools, reason across tasks, and take action in real workflows. That is why I believe we are approaching an inflection point, not just in AI adoption, but in whether AI finally starts doing meaningful work instead of creating more of it.

Similar pages

Browse jobs