Custom rule checks
Assert outcomes that match your pricing, product, compliance, and policy requirements.
Your APIs need to deliver the correct data in every scenario. Catch misconfigurations and align applications with internal and external business rules so your API stays the source of truth.
{"price": 184.32,"currency": USD,"stale_ms": 412,"spread_bps": 8.2}APIContext checks whether APIs return the right information for real scenarios: pricing, eligibility, compliance, routing, regional behavior, and other rules unique to your business.
Every business has its own policies, products, prices, regulatory requirements, and edge cases. Business rule checks make sure APIs deliver the right information, not merely a successful response.
1# pricing - quotes API2rule "quote_freshness" {3when route ~= "/quotes/*"4assert body.stale_ms < 15005severity critical6}78# reg-Z disclosure - APR cap by state9rule "apr_cap_state" {10when route == "/loans/calc"11let cap = state_cap(body.state)12assert body.apr <= cap13route_to "compliance@"14}
When APIContext finds a variance, teams can review the evidence, decide whether to update the API, change the application, or revise the rule, then get the right owner involved.
Rule price.list == catalog.price failed
{ sku: "SKU-3417", price.list: 24.99, catalog.price: 19.99, region: "TX", effective: "2026-04-01"}Business rule conformance issues are not generic application monitoring noise. Deliver alerts at the right cadence to compliance, architecture, product, or engineering teams.
Assert outcomes that match your pricing, product, compliance, and policy requirements.
Run checks across the edge cases where business logic failures usually hide.
Review request, response, assertion, and variance details before choosing the fix.
Send API, application, and rule issues to the teams that actually own them.
Notify compliance and architecture teams without flooding application monitoring queues.
Keep a history of failures, accepted variances, and remediation decisions.
Business-rule evidence routes cleanly into compliance, product, architecture, and engineering workflows
Define the business outcomes that matter, then let APIContext catch the API responses that violate them.