NTI-1 Verified Badge

Federated, post-quantum signed, zero-lock-in compliance certificates for AI agent projects.

Dilithium5 signed Multi-OIDC Offline verifiable Federated Zero data lock-in

Live badge

NTI-1 badge demo unverified demo

The problem this solves

Every enterprise deploying AI agents has the same question: "Is this agent actually secure, and can I prove it to an auditor?" Today, the answer is a marketing PDF. It cannot be verified. It cannot be trusted.

NTI gives every AI agent repo a portable, cryptographically signed compliance certificate that any third party can verify offline in seconds. No server. No subscription. No lock-in.


Why this is different

Traditional badgeNTI verified badge
Self-reported scoreOIDC + Dilithium5 signed
Vendor holds your dataYour repo holds the cert
GitHub onlyGitHub, GitLab, Azure, Google, custom
Cannot verify offlineVerify with one command, no network
CentralizedFederated — anyone can mirror

Install in 2 steps

1. Add this to .github/workflows/nti.yml

name: NTI Verify
on: [push, pull_request]
permissions:
  id-token: write
  contents: read
jobs:
  verify:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: abisheakp197/nti-badge@v1
      - name: Commit certificate
        run: |
          git config user.name "nti-bot"
          git config user.email "bot@nti.local"
          git add nti-certificate.json
          git commit -m "chore: NTI certificate [skip ci]" || true
          git push || true

2. Add the badge to your README

[![NTI-1 Verified](https://nti-badge-svs1.vercel.app/api/badge?repo=your-org/your-repo)](https://nti-badge-svs1.vercel.app/repo.html?repo=your-org/your-repo)

Verify any certificate offline

pip install nti-scanner
nti-scanner verify ./nti-certificate.json

No network. No NTI servers. Just math.


Federation

NTI is a protocol, not a product. Any company, university, or government can run their own mirror node. See the federation manifest for the full spec.


Endpoints

Links