Skip to main content
AuthForge ships an AGENTS.md file in the root of each official SDK repository. It is a single-file reference for correct licensing integration: constructor parameters, methods, server error codes, and copy-paste patterns (including what not to do).

​
Quick integration

Paste this prompt into your AI tool together with the AGENTS.md file from the SDK you use (add the SDK source to context if the agent should wire imports and project layout): 
Integrate AuthForge licensing into this project. 
My App ID is [YOUR_APP_ID] and App Secret is [YOUR_APP_SECRET].
The app should require a valid license to run.
Show the license key input on startup, validate it, 
and exit gracefully if the license is revoked or expires.
Refer to the AGENTS.md file for the SDK reference.
Replace the bracketed placeholders with your real credentials in a secure way (for example environment variables), not committed secrets.

​
Where to find AGENTS.md

Each file lives in the repository root of the matching SDK: Clone or browse the repo, open AGENTS.md, and attach it (or the raw file from the default branch) to your agent session.

​
Supported AI tools

This workflow works with Cursor, GitHub Copilot, Claude Code, Windsurf, and any assistant that can read project or pasted context files.

​
Tips for better results

  • Add both the SDK’s main source file (for example authforge.py, AuthForgeClient.cs) and AGENTS.md so the agent matches real APIs and naming.
  • State your language and framework explicitly (for example “.NET 8 WPF” or “Go CLI”).
  • Ask the agent to handle failure paths and server error codes, not only the happy path.
  • Compare generated code to the Do NOT section at the bottom of AGENTS.md before shipping.

​
llms.txt

For tools that support the llms.txt convention, a site-wide summary is available at https://docs.authforge.cc/llms.txt for high-level AuthForge concepts and SDK links.