yompal

7 ms·

1.
by yompal 2y ago
You're the best :) thanks for inspiring
2.
by yompal 2y ago
Fair question. Pydantic.ai looks like a wrapper around the client and closer to an agent framework. agents.json is not that. agents.json makes an existing API format like OpenAPI, interpretable to LLMs. This is done through tool selection a
3.
by yompal 2y ago
This SDK isn't meant to be restrictive. This can be implemented into other open-source frameworks as a plugin(ie. BrowserUse, Mastra, LangChain, CrewAI, ...). We just don't want someone like AWS to flip this into a proxy service.
4.
by yompal 2y ago
Not ignorant at all! This is our favorite question. MCP is taking a stateful approach, where every client maintains a 1:1 connection with a server. This means that for each user/client connected to your platform, you'd need a dedi
5.
by yompal 2y ago
We see the same vision you've described, and it'll take thoughtful execution and distribution on our part to continue to make agents.json the standard for tool use. I've been in touch with the AX team at Netlify since the art
6.
by yompal 2y ago
Funnily enough, a search tool to solve this problem was our product going into YC. Now it’s a part of what we do with wild-card.ai and agents.json. I’d love to extend the tool search functionality for all the tools in your belt It took us a
7.
by yompal 2y ago
The tail of the problem is quite long. Even if the average model is perfect at these things, do we want them to re-reason each time there's an impasse of outcomes? Often, the outcomes we want to achieve have well traversed flows anyway
8.
by yompal 2y ago
Interesting! Reach out if you want to chat about it :)
9.
by yompal 2y ago
That approach does a lot better, but LLMs still have positional bias problem baked into the transformer architecture ( https://arxiv.org/html/2406.07791v1 ). This is where the LLM biases selecting information earlier in
10.
by yompal 2y ago
Potentially. I also have reservations about it not technically being open source
11.
by yompal 2y ago
1) Thanks for being a part of the journey! We also want something that works for us as agent developers. We didn't feel like anything else was addressing this problem and felt like we had to do it ourselves. We love feedback! This is o
12.
by yompal 2y ago
No worries! In other cases, I believe you would be right. But splitting up context is not optional with MCP. Part of the whole state will always reside in an external entity.
13.
by yompal 2y ago
We're grateful that bigger players like Resend, Alpaca, etc do want to implement the protocol. The problem is honestly onboarding them fast enough. That's one of the main areas we're going to build out in the next few weeks.
14.
by yompal 2y ago
Bearish on everyone needing to be on stateful protocols. Developers should have the option to have their state managed internal to their application.
15.
by yompal 2y ago
llms.txt is a great standard for making website content more readable to LLMs, but it doesn’t address the challenges of taking structured actions. While llms.txt helps LLMs retrieve and interpret information, agents.json enables them to exe
16.
by yompal 2y ago
The end developer doesn't need to even see or read the agents.json file. It's a means for transparency and meant to be implemented by the API provider. Tooling to make creating an agents.json easier is on our roadmap. We have a pr
17.
by yompal 2y ago
A couple people have mentioned some relevant things in this thread. This SDK isn't meant to be restrictive. This can be implemented into other open-source frameworks as a plugin(ie. BrowserUse, Mastra, LangChain, CrewAI, ...). We just
18.
by yompal 2y ago
We work with API providers to write this file. It takes a non-negligible amount of thought to put together since we're encoding which outcomes would be useful to enable/disable for an LLM. The standard is open so anyone can write
19.
by yompal 2y ago
LLMs do well with outcome-described tools and APIs are written as resource-based atomic actions. By describing an API as a collection of outcomes, LLMs don't need to re-reason each time an action needs to be taken. Also, when an OpenAP
20.
by yompal 2y ago
It now reads "MUST provide the title of the `agents.json` specification file. ..." Thanks for the heads up!
21.
by yompal 2y ago
It's not that Arazzo can't work for LLMs, just that it's not the primary use case. We want to add LLM enabled transformations between linkages. Arazzo having to serve other use cases like API workflow testing and guided docs
22.
by yompal 2y ago
Yup. The specification is under Apache 2.0 and the Python package is under AGPL. The full licenses can be found here: https://docs.wild-card.ai/about/licenses
23.
by yompal 2y ago
We've been keeping a close eye on this topic: https://github.com/modelcontextprotocol/specification/discus... The options being considered to do this are: 1) maintain a session token mapping to the state -- w
24.
by yompal 2y ago
We've been in touch with Arazzo after we learned of the similarities. The long-term goal is to be aligned with Arazzo. However, the tooling around Arazzo isn't there today and we think it might take a while. agents.json is meant t
25.
by yompal 2y ago
MCP is great for the stateful systems, where shared context is a benefit, but this is a rarity. Developers generally write clients to use APIs in a stateless way, and we want to help this majority of users. That said, agents.json is not mut
26.
by yompal 2y ago
Thanks! MCP is taking a stateful approach, where every client maintains a 1:1 connection with a server. This means that for each user/client connected to your platform, you'd need a dedicated MCP server. We're used to writing
27.
by yompal 2y ago
That's a good point. I'll add a download button to the registry. The agents.json are also available here https://github.com/wild-card-ai/agents-json/tree/master/agen... EDIT: updated
28.
by yompal 2y ago
We think the main opportunity is to charge API providers, to get white-gloved onto this standard.
29.
Show HN: Agents.json – OpenAPI Specification for LLMs(github.com)
212 points by yompal 2y ago|69 comments
30.
Show HN: Agents.json – Open-source API specification for LLMs(github.com)
4 points by yompal 2y ago|0 comments

More ›