engomez

7 ms·

91.
by engomez 1y ago
Generally agree, we're targeting teams who need to make agents accessible to both their developers and non-developers in one platform. There's not really a way to do that as far as I know in any other framework. That said, I do fi
92.
by engomez 1y ago
Good question! Main things: n8n you can't export to code (or import). It's all visual, so you don't get CI/CD, typesafety, etc. when you want it. That can be fine if visual is all you need. Architecturally, n8n is good f
93.
by engomez 1y ago
We made a good video about the differences between n8n, OpenAI, and Inkeep here: https://youtu.be/tRgU5FQoe3s . Short overview. Re:OpenAI agents builder - there is a hard one-time ejection to code. You can export to their Ty
94.
by engomez 1y ago
Both work - Agents can be triggered via API just like any normal process, so they will go do the work async and post the result via e.g. an MCP of your choice to Slack, backend forms, etc. We don't have a built-in human-in-loop orchest
95.
Show HN: Inkeep (YC W23) – Agent Builder to create agents in code or visually(github.com)
79 points by engomez 1y ago|49 comments
96.
by engomez 2y ago
We measure the opposite now - % of questions where the bot was not able to find documentation to answer and it doesn't exist. This powers our insights reporting. We generally don't hear complaints about false positives here (i.e.,
97.
by engomez 2y ago
appreciate it!
98.
by engomez 2y ago
best way to frame the customer-facing AI: guided tutorials on-demand that can translate between user terminology and product lingo.
99.
by engomez 2y ago
appreciate it!
100.
by engomez 2y ago
Ah understood. I can see how the term is a little fuzzy. Glad it highlighted how the product works though.
101.
by engomez 2y ago
this one is designed for support agents - not to be customer facing. Whole goal is to make it more scalable to provide high-touch human-based support for teams who are keen on that. Agree customer-facing AI has to be done in a tasteful and
102.
by engomez 2y ago
that's the goal. And now with Keep the goal is to help the support team answer those questions that come through faster too. Minimizing "time to answer" across the funnel is the goal.
103.
by engomez 2y ago
glad to hear!
104.
by engomez 2y ago
Have been a Cursor user for ~1yr. I think they just nailed the key workflows people wanted - i.e. the fully conversational side bar with "apply" buttons and easily being able to attach the right files or code snippets you want. VS
105.
by engomez 2y ago
give the playground a shot and let me know what you think. we answer 250k+ customer-facing questions/mo today for teams who really care about quality (Anthropic, Clerk, Pinecone, Postman) - we're brining that same care and high ba
106.
by engomez 2y ago
ty!
107.
by engomez 2y ago
nothing like closing the content loop! try to make that direct.
108.
by engomez 2y ago
My understanding is that Q is a general purpose internal ai/search service - similar to Glean or Microsoft's equivalents. Our tool focuses on support use cases (customer-facing or internal-facing), which means we can go deep with
109.
by engomez 2y ago
Take a look at https://docs.inkeep.com/ai-api/openai-chat-completion-endpoi... tl;dr we define a JSON schema with a few semantic labels that represent a gradient in confidence. On our end we prompt it with certain exam
110.
by engomez 2y ago
was this in the support copilot or our public-facing bot on our landing page? for my fyi what did you mean by 'failures' of the service, can look to create some content relating to that.
111.
by engomez 2y ago
Not too bad - $3k.
112.
Launch HN: Inkeep (YC W23) – Copilot for Support (think Cursor for help desks)
117 points by engomez 2y ago|61 comments