Summary
find_agent exists because ids are the thing a model cannot guess and a human never remembers.
Every platform that addresses things by opaque id needs this tool and many skip it, leaving the caller to hard-code ids that break when something is rebuilt. Looking up by name is a small convenience that removes a whole class of brittle configuration. The scope requirement is the operational note: a general Langdock key will not work unless it carries Agent API rights.
What it is
Langdock's endpoint for calling the agents built in their platform. The surface is small because the work happens inside the agent, not in the protocol.
What you get
- find_agent — look up an agent's id by name, so the caller does not need to hold ids
- And the two remaining tools, covering invocation and its result
Requirements
A static API key holding the Agent API scope, in either an Authorization or x-api-key header.
Setup effort
Paste a URL with a key — add the endpoint to your client