Frequently asked questions

A rule engine for eligibility and pricing decisions. Instead of hardcoding "who qualifies" and "what it costs" into your application and redeploying every time a business rule changes, you define both as versioned, visual rules in Inzinx, then call one API to evaluate eligibility or compute a price in real time. Every call returns a full trace explaining exactly why it reached that result -- not just the answer.

No. Rules are built with a visual, drag-and-drop condition-tree editor (AND/OR/NOT logic, comparisons, table lookups, tiered brackets) directly in your dashboard, and every eligibility rule can also be viewed as an interactive flowchart. If you do need something the visual builder can't express, you can drop into a raw scripted expression for that one condition -- but it's never required.

Yes -- an eligibility rule can include another one of your rules as a condition, so shared logic (a base eligibility check every product line uses, for example) doesn't need to be copy-pasted across rules. The flowchart view expands these references inline so you can see exactly what's being evaluated, not just a name to look up separately.

Yes -- every new account gets 3 months free with a daily quota for both management calls (submitting/activating rules) and evaluation calls (evaluate/rate). No credit card is required to sign up.

Your rules and data are never deleted. Evaluate/rate API calls are blocked until you upgrade to a paid plan; you can still log in and manage your rules in the meantime.

Standard gives you 3x the Trial plan's daily quota, with self-service checkout right from your Billing page (Razorpay-hosted, cards and UPI). Enterprise is for high-volume production use and is contact-us only -- reach out and we'll set up billing directly.

Fill in the sign-up form and confirm your email via the link we send you. After that, an admin reviews and approves new accounts (usually within 24 hours) before you can log in -- this is a manual step we do for every new self-service account today, not an automated queue.

An eligibility rule answers a yes/no question ("does this qualify?") using condition trees. A rating rule computes an amount ("what does this cost?") by chaining ordered factors -- table lookups, tiered brackets, deductible curves, flat/percentage adjustments -- that apply in exactly the order you define.

Yes -- Decision Graphs let you wire eligibility checks, table lookups, rating rules, and raw scripted transforms together on a visual canvas, branching down different paths depending on whether an earlier check passes or fails. It's for cases where "first check eligibility, then look something up, then price it" needs to live as one reviewable, testable flow instead of several disconnected rules your application has to orchestrate itself.

Yes. Every draft rule has a "Test it" mode that runs real input against it and shows the full result and trace, without activating it or affecting your live API calls at all.

Yes -- describe what you want in plain English (e.g. "decline anyone under 18 or with more than 2 prior claims") and Inzinx drafts the condition tree for you to review and adjust before saving. Every rule -- however it was created -- also has a plain-English explanation and a set of auto-generated test scenarios available on its detail page, so you can sanity-check what it actually does.

Yes -- the Analytics dashboard shows pass/fail rates and which conditions reject the most, latency percentiles per rule type, which rules see zero traffic (a sign something may be safe to retire), and a time-window filter (24 hours, 7 days, or 30 days).

Rules, data, and API keys are isolated per account (tenant). API keys are stored as one-way hashes, never in plain text; passwords are hashed with bcrypt. Login supports optional two-factor authentication (TOTP/Google Authenticator) plus automatic lockout after repeated failed attempts. See our Security page for the full picture, including independent external testing (SSL Labs, OWASP ZAP, Greenbone/OpenVAS) and how to report a vulnerability.

Yes -- once you're signed up, generate your own API keys from Dashboard → API keys (separate from your login, one for each integration you run). See our Developers page for the full REST API reference: authentication, request/response shapes, and worked examples.

Nine, chained in whatever order you define: flat (a fixed multiplier or addend), condition-based (only applies if a condition passes, e.g. a bundling discount), table lookup (reads a factor from a named rate table by an input value -- exact match or a numeric range like an age band), tiered/bracket (a progressive charge across brackets of a value, like a tax bracket), deductible curve (a factor read off a curve of points, optionally interpolated between them for continuous scoring), a raw scripted expression for formulas the others can't express, a reference to another rating rule (so shared pricing logic can be composed, not copy-pasted), a persistent accumulator (a running total tracked across calls, e.g. an annual deductible paid-to-date), and a reinsurance-style excess-of-loss layer.

A named, versioned lookup table your rating rules can reference (via the table-lookup factor kind) -- e.g. a territory-to-factor mapping or an age-band table. Like rules, tables have their own draft/active lifecycle and full version history, and can be scoped by effective date and region. Tables also support DMN-style hit policies (First, Unique, or Collect Sum/Min/Max/Count) for when more than one row could match the same lookup value, and can be authored with a keyboard-first grid -- arrow keys and Tab to move between cells, Enter to add a row, and pasting a block copied straight from Excel or Google Sheets.

Email hello@inzinx.com -- we're a small team actively shipping based on real feedback.