Service policy · updated August 20, 2026
Clear terms for a small, deterministic service.
InstructLint audits public GitHub repositories without changing them. These notes explain the data path, payment settlement, report delivery, and support process.
Service scope
InstructLint reads a bounded snapshot of a public GitHub repository and compares agent-facing instruction files with observable repository evidence. It does not access private repositories, write to repositories, or apply suggested patches.
Reports are deterministic, best-effort developer guidance. They may be incomplete or contain mistakes, so review every finding and patch before relying on it.
Payment and delivery
The free preview requires no payment. The full report endpoint returns an x402 v2 challenge stating the exact USDC amount, recipient, and Base network before a compatible client authorizes payment. InstructLint never asks for a private key.
Payment settles only after the full report handler returns a successful response. Invalid input, unsupported repositories, GitHub retrieval failures, and other error responses are not settled. A successful response includes the report and an x402 payment receipt header.
Delivery support and refunds
If an on-chain payment settles but your client does not receive a usable report, open a public support issue within 14 days. Include the transaction hash and public repository URL. Never post a private key, seed phrase, or payment signature.
The operator will first reproduce or re-deliver the purchased report. If delivery cannot be restored after the payment is verified, the settled report price will be returned to the paying address. Third-party network fees are not refundable.
Open a paid-report support issue →Privacy
Data processed
A request contains a public GitHub repository URL. During the request, the service fetches a bounded set of public repository files and returns an audit. The application has no account system, cookies, advertising tracker, or analytics script.
Storage and providers
InstructLint does not intentionally persist repository snapshots or audit results in an application database. Hosting and upstream providers may process request metadata in their operational logs. The service relies on Vercel for hosting, GitHub for public source retrieval, PayAI for x402 facilitation, and Base for public USDC settlement. The Web3ToolLaunch directory serves the footer badge image and may receive ordinary request metadata when that image loads. On-chain transaction details are public by design.
Acceptable use and changes
Use the service only for lawful analysis of public repositories. Do not attempt to bypass limits, interfere with the service, or submit private or secret material. The operator may restrict abusive traffic to protect availability.
Material policy changes will be published on this page with an updated date. Continued use after a change means the current terms apply to that request.