What are Fingerprints?
Code fingerprints provide tamper-evident verification that an agent’s code hasn’t changed since credential issuance. How it works:- CLI generates SHA256 hash of all files matching include/exclude patterns
- Fingerprint stored in agent manifest
- Verifiers can regenerate fingerprint and compare
- If fingerprints don’t match → code was modified
Initializing Agent Manifests
Interactive Mode (Default)
Non-Interactive Mode
With Custom Configuration
Force Overwrite
Configuration File (.beltic.yaml)
Create.beltic.yaml in your project root:
Fingerprint Generation
Basic Fingerprint
- Current directory as root
- Patterns from
.beltic.yamlor defaults - Updates
agent-manifest.jsonautomatically
Verify Mode (Don’t Write)
With Dependency Fingerprints
Verbose Output
Custom Manifest Path
Custom Config
Deployment Types
Standalone
Single codebase, one agent:Monorepo
Multiple agents in one repository:Embedded
Agent embedded in larger application:Plugin
Agent as plugin/extension:Serverless
Agent as serverless functions:Include/Exclude Patterns
Glob Patterns
Include all TypeScript:Common Patterns
Node.js project:Workflow Integration
Development Workflow
CI/CD Integration
Pre-commit Hook
Best Practices
- Include only production code - Exclude tests, builds, dependencies
- Use .beltic.yaml - Version control your fingerprint configuration
- Verify in CI - Catch fingerprint mismatches before deployment
- Update after every code change - Keep fingerprints current
- Document exclusions - Comment why files are excluded
Next Steps
Signing & Verification
Sign your manifest as a credential
Command Reference
Complete CLI command documentation
AgentCredential
Complete agent credential specification