RuleOps exposes a small server-side API for discovering published rules, evaluating a rule in your product flow, reading the persisted decision trace, and syncing reference library values used by rule fields.
1. Authenticate
Send your live key as a Bearer token from your backend.
2. Discover schema
Read rule fields, required inputs, and any field-specific library codes.
3. Evaluate
Send validated inputs to the rule evaluator and store the trace id.
4. Audit
Load decision traces later for support, reconciliation, and review.
Base URL
/api/v1Endpoint map
The MVP API is intentionally compact. Use the menu for full request and response docs.
Rules
/rules/rules/{rule_id}/rules/{rule_id}/evaluateDecisions
/decisions/{trace_id}Libraries
/libraries/libraries/{library_code}/libraries/{library_code}/recordsConventions
Responses are JSON and return no-store cache headers.
Rules use the latest published version unless a version is pinned. Pin a version in production when input-schema changes should require an explicit integration update.
Archived rules cannot be discovered, retrieved, or evaluated.
Decisions are always Approve, Reject, Review, Escalate, or Custom. A Custom decision carries its configured value in output.message.
Library-backed rule fields expect record codes from their own library, not display names.
Evaluate supports idempotency for retry-safe business actions.
Primary evaluation path
/api/v1/rules/{rule_id}/evaluateUse this inside your application workflow when RuleOps must make or explain a decision.