Integrations — Sagewai works with the tools you already use

This is Tier 3 of the example catalogue — specific developer-tool and registry integrations. Goal: "Sagewai works with the tools you already use."

These examples target a specific audience — the developer-tools market and registry users. They're reference-grade for that audience, not the SDK's main story. If you came here for the "add AI to my product this quarter" story, jump back to the Lighthouse section.

CLI proxies

Sagewai can act as a transparent proxy in front of popular AI CLIs, adding observability, cost tracking, and Sealed-spine credential handling without changing the developer's day-to-day surface.

When to read: when your team is already using one of these CLIs and you want to add observability and cost tracking without changing their workflow.

Agent registry

Publish and consume agents through the Sagewai registry. The registry is the discovery surface for agents you want other teams (or other companies) to invoke.

When to read: when you're shipping an agent that other teams should be able to invoke without re-implementing the integration.

Harness primitives

The Harness is Sagewai's surface for power users who want fine-grained control over the proxy + agent boundary.

When to read: when you're integrating Sagewai into an existing tool surface and need direct access to the harness primitives.

What to read next

• Lighthouse — the production-grade examples that solve real-world problems.
• Foundation — the SDK basics if you're starting from zero.
• Patterns — Tier 4 reference examples.
• Reference — examples — the full numbered list.