Help: OpenClaw keeps hallucinating API endpoints that don't exist.

I've been using OpenClaw for a few weeks to generate API integration code, mostly in Python. I keep running into a frustrating issue: it confidently suggests API endpoints and parameters that aren't in the actual service documentation.

For example, last week it told me to use a `GET /api/v2/users/me/preferences` endpoint for a popular SaaS tool. That endpoint simply doesn't exist—the correct one is `/api/v1/user/settings`. I had to debug a bunch of 404s before I realized the problem.

Has anyone else hit this? Is there a way to reduce these kinds of hallucinations, or is it just a known limitation of the current model? I like the speed but the inaccuracies are costing me more time than they save.