anti-hallucination

To prevent API hallucinations, you can trigger a verification protocol that identifies your project's tech stack and cross-references API existence and behavior against official documentation before implementation.

You can verify external API existence by running a protocol that detects your tech stack dependencies and requires manual checks against official documentation and references to ensure accurate behavior.

Citing documentation before implementing payment APIs ensures accurate references and prevents incorrect integration, which is critical for security-sensitive areas like auth, payments, and data persistence.

Yes, the protocol performs stack detection to identify your project's dependencies, making it applicable to coding tasks involving external APIs across various tech stacks.

The best way to ensure API reference accuracy is to enforce a never-assume guideline that requires manual verification and documentation checks specifically for critical APIs like auth and payments.

Yes, the protocol requires manual verification and documentation checks to confirm API existence and behavior, ensuring you do not assume an API exists without proper verification.