[arjunchint]

I am not following a couple of things:

- you sell to websites an in-app agent

- why not just have them give you API spec, why reverse engineer their APIs?

A bit longer term, would you see yourself competing with WebMCP then? Because the website can just expose those APIs to any browser agent

[pancomplex]

Even with an API spec it wouldn't "just work". You'd still need to handle authentication and have a place to manage which APIs you want the in-app agent to have access to / when to call a given tool.

And believe it or not, even big companies with big eng teams don't have API specs available for their applications ¯\_(ツ)_/¯

[johnpaulkiser]

Yeah the auth angle and unobtrusive integration path seems like the real neat thing here. From your customers eyes its just another user account right?

Is that a requirement to integrate it? your app has to essentially have "teams" or at least shared resources?

[pancomplex]

Yup just another user account. It can work without this as well (we support ingesting other resources such as help center articles, pdfs, etc.) but at that point it's no different from any other (dumb) AI chatbot out there that just spits out a bunch of itemized bullets.