The certification API runs the Thermodynamic Coherence Engine (TCE) on your published circuits to verify that they achieve circuit closure (Phi_c = 1).
Certify a Circuit
POST /v1/circuits/:pid/certify
Submit a circuit for certification.
curl -X POST https://registry.brik64.dev/v1/circuits/cir_abc123/certify \
-H "Authorization: Bearer brik_live_xxx"
Response:
{
"pid": "cir_abc123",
"certified": true,
"phi_c": 1.0,
"tce_metrics": {
"information_entropy": 0.0,
"closure_domains_verified": 3,
"closure_domains_total": 3,
"monomers_used": 5,
"composition_depth": 2,
"eva_operators": {
"sequential": 3,
"parallel": 1,
"conditional": 0
}
},
"hash": "7f2a9b3c...",
"certified_at": "2026-03-21T00:00:00Z"
}
Phi_c = 1.0 means the circuit is fully closed — all inputs are consumed, all outputs are produced, and information entropy is zero. This is the formal guarantee of Digital Circuitality.
Certification Failures
If the circuit does not achieve closure:
{
"pid": "cir_abc123",
"certified": false,
"phi_c": 0.87,
"errors": [
{
"type": "unclosed_domain",
"domain": "temperature",
"message": "Domain 'temperature' has unverified bounds at line 14"
}
]
}
Verify a Certification
POST /v1/circuits/:pid/verify
Re-verify an existing certification. Useful for auditing or confirming that a previously certified circuit still passes.
curl -X POST https://registry.brik64.dev/v1/circuits/cir_abc123/verify \
-H "Authorization: Bearer brik_live_xxx"
{
"pid": "cir_abc123",
"verified": true,
"original_hash": "7f2a9b3c...",
"current_hash": "7f2a9b3c...",
"match": true,
"phi_c": 1.0
}
Rate Limits
| Tier | Certifications/day | Verifications/day |
|---|
| Free | 10 | 50 |
| Pro | Unlimited | Unlimited |
Certification is computationally intensive. Free-tier users are limited to 10 certifications per day. Verifications are cheaper and have a higher limit.
Certification Badge
Certified circuits receive a badge URL that can be embedded in READMEs or documentation:

The badge displays the Phi_c score and certification date.