zctl bridge start --bind 0.0.0.0:8080 --translate zardaxt:// to http:// Now you can use a standard HTTP POST:
zctl link create --app-id $APP_UUID --model fraud_detection --expiry 30d zardaxt os scoring link
Scoring link created successfully: zardaxt://scoring/v3/evaluate?model_id=fraud_detection_v2&apikey=zXkL9qP2mN8vR4tY&tenant=acme_corp&signature=sha256-abc123 curl -X POST "zardaxt://scoring/v3/evaluate?model_id=fraud_detection_v2&apikey=zXkL9qP2mN8vR4tY" \ -H "Content-Type: application/json" \ -d '"amount": 5000, "user_id": "U123", "country": "NG"' Response: zctl bridge start --bind 0
curl -X POST http://zardaxt-bridge:8080/scoring/v3/evaluate?model_id=fraud \ -H "X-API-Key: zXkL9qP2" -d '"user_action": "login"' Zardaxt OS provides a CGO-free client library. Never Hardcode Links in Source Code Use a secrets manager (e
"score": 0.87, "risk_level": "high", "latency_us": 342 Because scoring links often carry sensitive data (and API keys), securing them is paramount. Here are five non-negotiable rules: 1. Never Hardcode Links in Source Code Use a secrets manager (e.g., HashiCorp Vault, AWS Secrets Manager) to inject scoring links at runtime. 2. Enable Signature Validation Zardaxt OS supports HMAC signing. Generate a signed link: