Welcome to Intello

Every team that ships software depends on APIs they don't control. Stripe deprecates a field. OpenAI renames a parameter. Your billing flow breaks on a Tuesday and you find out from a customer email.

Intello watches those APIs for you and tells you — in the channel where you actually work — the moment something changes that matters.

What you'll see, day to day

You set up an integration once. After that, Intello quietly checks the API's contract on a schedule and sends you alerts shaped like this:

Breaking   Stripe removed customer.email_verified from GET /customers/:id — your billing service references this field. Triage in app.

Three things make that alert useful:

1. Severity. Safe additions, Risky tightenings, Breaking removals — each routed differently.
2. Impact. Intello knows which of your services touch which endpoints, so the alert tells you what's likely to break.
3. One thread per cause. A single schema change that touches twelve routes is one alert, not twelve.

That's the whole product. Everything else in these docs exists to make that loop tighter for your team.

Who Intello is built for

• Engineers who own integrations and are tired of finding out about API changes from PagerDuty incidents.
• Platform leads who need a defensible answer to "how do we know when a vendor breaks us?"
• Anyone evaluating tools for vendor API observability who wants the trial to work in five minutes, not five hours.

What Intello is not

It's not a gateway, a proxy, or a request-tracing tool. It doesn't sit in your traffic path. It reads published API specs, compares snapshots over time, and surfaces what changed. Pair it with your existing tests and observability — Intello fills the gap they don't cover.