API Robots ๐Ÿค–๐Ÿš€

326 posts

API Robots ๐Ÿค–๐Ÿš€ banner
API Robots ๐Ÿค–๐Ÿš€

API Robots ๐Ÿค–๐Ÿš€

@APIRobots

Your API ๐Ÿค– partner. We craft ๐Ÿ”จ cutting-edge REST APIs to drive ๐Ÿš— innovation and connect your systems seamlessly. ๐Ÿค Expert API development solutions.

Lab ๊ฐ€์ž…์ผ Ekim 2023
203 ํŒ”๋กœ์ž‰63 ํŒ”๋กœ์›Œ
๊ณ ์ •๋œ ํŠธ์œ—
API Robots ๐Ÿค–๐Ÿš€
API Robots ๐Ÿค–๐Ÿš€@APIRobotsยท
โœ… Explore our vast ecosystem of APIs ๐Ÿงฉ We've got 50+ APIs covering everything from finance, crypto, vin decoders, streaming services to motivation. Dive in and supercharge your app today! #RestAPI #API apirobots.pro/apis/
English
0
0
1
87
API Robots ๐Ÿค–๐Ÿš€
API Robots ๐Ÿค–๐Ÿš€@APIRobotsยท
Made $10K for 30 days! #buldinpublic #indiehacker #microsaas
Borixo ๐Ÿ“ฑ๐Ÿš€@BorixoMobile

๐Ÿš€ Just launched Indie Hacker Simulator on @itchio! Build a startup from $0 โ†’ $10K MRR in 30 days โšก Balance coding, marketing & energy ๐ŸŽฎ Retro pixel art style ๐Ÿ’ก Multiple paths to success Can you make it? borixo.itch.io/indie-hacker-sโ€ฆ #indiegame #gamedev #indiedev #indiehacker

English
0
0
1
28
Roy Derks ๐Ÿš€
Roy Derks ๐Ÿš€@gethackteamยท
Is there a MCP server for the X API? (cannot find one that actually works...)
English
3
0
2
328
API Robots ๐Ÿค–๐Ÿš€
API Robots ๐Ÿค–๐Ÿš€@APIRobotsยท
@dan_starns That is impressive, we are building a service for converting APIs to MCP, and one of the main issues is the big number of tools available, do you think your project can help with this?
English
1
0
0
32
Dan Starns
Dan Starns@dan_starnsยท
Been building with MCP servers lately and kept exhausting my API limits with 90+ tools loading on every request ๐Ÿ˜… So I built MCP-RAG - a TypeScript wrapper for AI SDK that uses vector search + Neo4j to semantically select only the relevant tools you actually need. Went from 47K tokens down to 5K while keeping 100% accuracy. Basically, your agent doesn't need to see every tool on every request. Let it search instead. Open source, benchmarked, ready to use. GitHub, npm, and full breakdown below ๐Ÿ‘‡ rconnect.tech/blog/semantic-โ€ฆ
English
2
3
8
499
eric zakariasson
eric zakariasson@ericzakariassonยท
if you could extend @cursor_ai, what would you build? think plugins to tweak chat + ui, hooks into internal agent APIs, full editor extensibilityโ€ฆ curious to hear!
eric zakariasson tweet media
English
350
17
441
77K
API Robots ๐Ÿค–๐Ÿš€
API Robots ๐Ÿค–๐Ÿš€@APIRobotsยท
@svpino Could we create a good MCP based on a RESTful API by limiting the tools and combining endpoints into more behavioral tools?
English
0
0
0
5
Santiago
Santiago@svpinoยท
The Model Context Protocol (MCP) is not just "another API lookalike." If you think, "Bro, these two ideas are the same," it means you still don't get it. Let's start with a traditional API: An API exposes its functionality using a set of fixed and predefined endpoints. For example, /products, /orders, /invoices. If you want to add new capabilities to an API, you must create a new endpoint or modify an existing one. Any client that requires this new capability will also need modifications to accommodate the changes. That issue alone is a colossal nightmare, but there's more. Let's say you need to change the number of parameters required for one endpoint. You can't make this change without breaking every client that uses your API! This problem brought us "versioning" in APIs, and anyone who's built one knows how painful this is to maintain. Documentation is another issue. If you are building a client to consume an API, you need to find its documentation, which is separate from the API itself (and sometimes nonexistent.) MCP works very differently: First, an MCP server will expose its capabilities as "tools" with semantic descriptions. This is important! Every tool is self-describing and includes information about what the tool does, the meaning of each parameter, expected outputs, and constraints and limitations. You don't need separate documentation because the interface itself is that documentation! One of my favorite parts is when you need to make changes: Let's say you change the number of parameters required by one of the tools in your server. Contrary to the API world, with MCP, you won't break any clients using your server. They will adapt dynamically to the changes! If you add a new tool, you don't need to modify the clients either. They will discover the tool automatically and start using it when appropriate! But this is just the beginning of the fun: You can set your tools so they are available based on context. For example, an MCP server can expose a tool to send messages only to those clients who have logged in first. There's a ton more, but I don't think I need to keep beating this dead horse. AI + MCP > AI + API *micdrop*
English
160
300
2.7K
574.6K