Skip to main content
The Beltic specification repository defines credential schemas, validation rules, and evaluation methodologies.

​
Beltic-Spec Repository

The official specification lives in the beltic-spec repository (currently private). Request early access to get started. 
beltic-spec/
├── docs/                    # Specification documents
│   ├── overview.md
│   ├── developer-credential-v1.md
│   ├── agent-credential-v1.md
│   ├── evaluation-metrics-v1.md
│   └── nist-mapping-v1.md
├── schemas/                 # JSON Schema files
│   ├── developer/v1/
│   └── agent/v1/
├── examples/                # Test fixtures
│   ├── developer/v1/tests/
│   └── agent/v1/tests/
└── scripts/                 # Validation scripts
    ├── validate_all.py
    └── test_conditional_rules.js

​
Using Schemas Locally

​
Get Repository Access

# Repository is currently private
# See /docs/early-access for access requests
Once you have access: 
cd beltic-spec

​
Validate with AJV

npm install -g ajv-cli ajv-formats

ajv validate \
  -s schemas/developer/v1/developer-credential-v1.schema.json \
  -d my-credential.json

​
Validate with Python

pip install jsonschema

python3 scripts/validate_all.py

​
Using npm Scripts

npm run validate:developer  # Validate all developer examples
npm run validate:agent      # Validate all agent examples
npm run test:conditional-rules  # Test 27 conditional rules

​
Credential Specifications

​
DeveloperCredential v1

Complete specification for developer identity and KYB verification. See: DeveloperCredential Reference

​
AgentCredential v1

Complete specification for agent technical profile and safety metrics. See: AgentCredential Reference

​
Versioning

Schemas follow semantic versioning:
  • v1.x: Current stable version
  • v2.x: Future version (breaking changes)
Backwards compatibility: v1 schemas remain stable. New features added as optional fields.

​
Contributing

To propose changes:
  1. Open issue in beltic-spec repository
  2. Discuss with maintainers
  3. Submit PR with schema updates
  4. Update documentation
  5. Add test fixtures

​
See Also