Launching today
UseAgents
Define tools once for agents use them everywhere
38 followers
Define tools once for agents use them everywhere
38 followers
LLMs have frozen knowledge and struggle to find tools. UseAgents solves this with a real-time registry where developers define their tools and APIs so AI agents can discover and use them instantly. No scraping, no guessing, just structured tools designed for agents. Build smarter AI systems with infrastructure made for the agentic web.
This is an interesting problem to tackle. A lot of agent workflows still break because tool discovery is messy, outdated, or too dependent on manual context stuffing. Having a real-time registry designed for agents feels like a cleaner direction, especially if it helps reduce all that guessing.
Curious, what kind of tools are getting defined first on UseAgents, internal dev tools, public APIs, or something else?
UseAgents
@akshay_kumar_hireid That’s exactly the problem I kept running into ,a lot of agent workflows feel fragile because of how messy tool discovery and context feeding still is.
Right now it’s a mix, but leaning more toward internal dev tools and smaller APIs. The first few tools are things people already use in their workflows but want agents to interact with more reliably.
I think early on it’ll be more dev-focused tools, then gradually expand to more public APIs as the ecosystem grows.
Curious what kind of tools are you currently using with agents?
UseAgents
this actually makes sense tbh. one of the weirdest things with agents right now is they can sound smart but still have no clean way to know what tools even exist. having developers define tools once and let agents discover them properly feels like something the ecosystem probably needs.
curious, do you see this becoming more useful for individual builders first or platforms trying to expose tools to lots of agents?
UseAgents
@nayan_surya98 Yeah, that’s exactly the gap I’m seeing agents can reason well, but actually knowing what tools exist and how to use them is still messy.
I think it’ll start with individual builders first, especially people already experimenting with agents and MCP tools. They feel the pain immediately.
But longer term, I see it becoming more valuable for platforms exposing tools to many agents that’s where having a standard way to define and discover tools really starts to matter.
Curious how you’re currently handling tools in your workflows?
Love the concept of a real-time tool registry for AI agents — this solves such a real pain point. Agents hallucinating tool capabilities or working with outdated APIs is one of those silent killers in agentic workflows. How does UseAgents handle versioning when a tool schema changes? Do connected agents get notified, or do they need to re-fetch capabilities on each run?
UseAgents
@sai_tharun_kakirala That’s a great question versioning is something I’m actively thinking about.
Right now, the idea is that tools are defined in a structured way and agents can fetch the latest schema, so they’re always working with up-to-date capabilities instead of stale definitions.
Longer term, I’m exploring versioned schemas so changes don’t break existing workflows, along with ways for agents to be aware of updates rather than blindly relying on old context.
Still early here, so I’d love to understand how you’d expect this to work in your own workflows.
@evanssmaina That makes a lot of sense — fetching the latest schema keeps things simple early on.
In practice though, I’ve seen “always fetch latest” become risky once workflows get more complex. Even small schema changes can silently break assumptions mid-run.
What I’d expect (or prefer) is a hybrid approach:
• Default to latest for discovery
• Allow agents to “pin” a schema version for critical workflows
• Push notifications / diffs when breaking changes happen
Almost like how APIs evolved with versioning + deprecation windows.
Also curious — are you thinking about letting agents declare compatibility (like “works with v2–v4”), or is that overkill at this stage?