So I built a few API calls for sales research purposes, mainly to help people gather better information about their prospects and leads.
The API can currently find LinkedIn profiles with around a 75% success rate, and it can also return decision-makers together with their LinkedIn profiles.
Where I’m struggling now is making the API more useful and reliable for AI agents. It’s not bad at the moment, but I’ve received feedback that Claude often “loses memory” of the API key, available endpoints, or what the API is supposed to do, even when the API key and documentation were provided in the conversation.
My current hypothesis is that this may be strongly connected to a poor documentation structure or schema. Maybe the docs are not clear enough for an agent to understand when and how to use each endpoint consistently.
Has anyone had a similar experience with Claude or other AI agents losing context, even when the API key and documentation were already shared?
I’d be very curious to learn how you solved it — especially around documentation structure, OpenAPI schemas, endpoint naming, examples, or agent-friendly API design.
답글 남기기