Welcome to Intello

Every team that ships software depends on third-party APIs it doesn't control. Vendors deprecate fields, rename parameters, and tighten validation without notice — and the failures often surface first as customer-reported incidents.

Intello monitors those APIs on your behalf and notifies you — in the channel your team already uses — as soon as the next scheduled sync detects a change that matters.

What you'll see, day to day

You configure an integration once. From then on, Intello checks the API's contract on a schedule and sends alerts in the following format:

Breaking   Stripe removed customer.email_verified from GET /customers/:id — tagged billing. Triage in app.

Three properties make these alerts actionable:

1. Severity. Safe additions, Risky tightenings, and Breaking removals are classified and routed independently.
2. Impact. Each change is tagged with the API domain it affects — billing, catalog, auth, and so on — so the alert clearly identifies which area of your integration is impacted.
3. One alert per cause. A single schema change that touches twelve routes is delivered as one alert, not twelve.

That is the core of the product. Intello is not a gateway, proxy, or request-tracing tool — it does not sit in your traffic path. The rest of this documentation exists to help you tighten that workflow for your team.

Who Intello is built for

• Engineers who own integrations and need to learn about upstream API changes before they cause incidents.
• Platform leads who require a clear, defensible answer to "how do we know when a vendor breaks us?"
• Teams evaluating vendor-API observability tooling who expect a working trial in minutes rather than hours.