Opt In to Anthropic’s OSS Scanner & Check Eligibility

Anthropic’s OSS scanner helps open-source projects get free access to Claude API credits. This guide walks you through opting in and verifying your project meets the eligibility requirements. You’ll need a GitHub account and a repository that qualifies as open source.

What You’ll Need

• A GitHub account with a public repository
• An Anthropic account (you can create one during the process)
• Your project must have an OSI-approved open-source license (e.g., MIT, Apache 2.0, GPL)
• The repository must be actively maintained (recent commits, not archived)

Step-by-Step

1. Check your project’s license. Open your repository on GitHub and look for a LICENSE file. If it’s missing, add one. Anthropic requires an OSI-approved license. If you’re unsure, visit the Open Source Initiative’s website to see the approved list.
2. Ensure your repository is public. Go to your repo’s Settings, then under “General” scroll to “Danger Zone.” If it says “Make public,” click it and confirm. The scanner can only access public repos.
3. Visit the Anthropic OSS scanner page. Navigate to https://www.anthropic.com/oss (or the direct scanner link if provided). You’ll see a form asking for your GitHub repository URL.
4. Enter your repository URL. Copy the full URL from your browser (e.g., https://github.com/yourname/yourrepo) and paste it into the input field.
5. Sign in with GitHub. Click the “Sign in with GitHub” button. This authorizes Anthropic to read your repository metadata. You’ll be redirected to GitHub’s authorization page—review the permissions and click “Authorize anthropic.”
6. Wait for the scan. After authorization, Anthropic’s scanner runs automatically. It checks the license, public visibility, and repository activity. This usually takes under a minute.
7. Review the result. You’ll see either “Eligible” or “Not eligible.” If eligible, you’ll get instructions to claim your API credits. If not, the page will typically list the reason (e.g., “No license found”).
8. Claim your credits. If eligible, click the “Claim” button. You’ll be asked to sign in to your Anthropic console or create an account. Follow the prompts to link your GitHub account and receive the credits.
9. Verify the credits appear. After claiming, go to your Anthropic console’s Billing page. You should see a credit balance (e.g., $50 or $100). If not, wait a few minutes and refresh.

Common Mistakes

• Using a non-OSI license. Licenses like “MIT License” are fine, but custom or “Creative Commons Non-Commercial” licenses may be rejected. Double-check the exact license name.
• Repository is private. The scanner cannot see private repos. You must make it public before applying.
• Forked repositories. If your project is a fork of another project, make sure you’ve made substantial changes. Some programs require the fork to be a distinct project.
• Archived or inactive repos. If your last commit was months ago, the scanner may flag it as inactive. Consider making a recent commit before applying.
• Entering the wrong URL. Double-check for typos. Use the full URL including https://.

Tips

• Update your README. A clear README with project description and usage instructions helps demonstrate your project is real and maintained.
• Add a license file. If you’re unsure how, GitHub’s “Add file” > “Create new file” and name it LICENSE. GitHub will offer templates.
• Use the same email. Ensure the email associated with your GitHub account matches the one you use for Anthropic to avoid confusion.
• Check your repository’s “About” section. Make sure the “Topics” include relevant keywords like “open-source”—it’s not required but can help.
• Apply when your project is active. If you’re about to make a big push, do it before applying so the scanner sees recent activity.

Troubleshooting

“Not eligible” without a reason. Try these in order:

1. Re-check your license file. It must be named LICENSE or LICENSE.md and contain the full license text.
2. Make sure your repo is public. Go to Settings > General > Danger Zone and confirm.
3. Wait 24 hours after making changes—the scanner may cache results.
4. Contact Anthropic support via the OSS page’s contact link, providing your repo URL.

GitHub authorization fails. Clear your browser cache, disable ad blockers, and try again. If the page loops, try a different browser.

Credits don’t appear. Check your Anthropic console’s Billing page. If it’s empty, log out and back in. If still missing, contact support with your GitHub username and the date you applied.

Frequently Asked Questions

Q: How long does the scan take?
A: Usually under a minute. If it takes longer, refresh the page after a few minutes.

Q: Can I apply for multiple repositories?
A: The program typically allows one application per GitHub account. Check the terms on the OSS page for current limits.

Q: What if my project uses a license not on the OSI list?
A: It will likely be rejected. Consider switching to an OSI-approved license, but only if it’s appropriate for your project.

Q: Do I need to have an Anthropic account first?
A: No, you can create one during the claim process. You’ll need to verify your email.

Q: Are credits recurring or one-time?
A: Typically one-time, but the program may offer renewals for active projects. Check the OSS page for details.

Q: Can I apply if my project is a personal tool not widely used?
A: Yes, as long as it meets the eligibility criteria. Popularity is not a stated requirement.

Related

• How to Block and Report Spam Emails in Yahoo Mail
• DNS Refresh Rate: How Often It Updates
• AI Agent Failure Detection Beyond Dashboards