Skip to content

Showcase agents / Self-Healing API

Platform / API teams

Self-Healing API

What problem? API schema renames break consumers silently — platform teams need detect → classify → remediate → validate with full audit trail.

Flagship product wedge: detect contract breaks → classify with SLM → safe remediate → validate → canary → promote or rollback.

tenant: tenant-apiheal-corpport :9106scenario: schema_rename
Inferix console view for Self-Healing API

What Inferix observes

Every run dual-writes to LensAI and TraceForge. Switch to this tenant in the console to see live KPIs.

  • TraceForge — heal funnel: diff → classify → patch → validate
  • LensAI — $/successful heal and canary SLO
  • DriftWatch — contract pass-rate slice
  • RouteIQ — capability deny matrix for SLM vs Claude

Tools & models

Real SQLite backends, not mocked HTTP stubs.

  • openapi.diff
  • contract.run_suite
  • gateway.get_canary
  • gateway.rollback_canary
  • adapter.patch
  • fixtures.update
  • auth.probe_scopes
  • deploy.mark_version

Model routing

  • Static OpenAPI lint (no LLM)
  • slm-apiheal-v* (classify/narrate only)
  • Claude (heal proposals — SLM denied write tools)

Try it

Start the stack, then run the golden scenario. Traffic appears in the console within seconds.

1. Start stack + agents

cd inferix && ./run-inferix.sh --full --agents

2. Golden scenario

curl -s -X POST http://localhost:9106/scenarios/schema_rename | jq

Expect HTTP 200 with JSON status and tool steps. Traces appear under this tenant in ~10s.

3. All agents at once

cd inferix && ./scripts/generate-agent-traffic.sh

Expected: JSON with status and tool steps. Then open the tenant console and filter traces by tenant-apiheal-corp. In-browser runner stays deferred — curl is the verified path.

Console: /console/overview?tenant_id=tenant-apiheal-corp · API traces: GET /v1/traces?tenant_id=tenant-apiheal-corp

See all seven agents in the console

Multi-tenant super-dashboard. Filter by tenant, drill into traces and costs.