Intello watches every spec your product depends on — OpenAPI, GraphQL, MCP. When something shifts, we classify it, route it, and tell the right person before it hits production.
api.stripe.com/openapi.json
200 OK · 14.2 kb · etag unchanged since 2m ago
Plug in a spec once. Intello captures the baseline, watches it on a schedule, and pushes an actionable alert to the people who can fix it.
Paste an OpenAPI URL, drop a GraphQL schema, or push on every build. One workspace, every integration you depend on — no agents, no proxies, no infra to stand up.
https://api.stripe.com/openapi.json
polling · every 1h
hubspot-graphql.schema.graphql
uploaded · 3m ago
github · acme/payments
ci push · feat/v2
Intello snapshots the first version, stores a clean diff on every poll, and keeps the entire history searchable. Polling runs on your schedule — every 1 to 12 hours.
Each change is classified breaking, risky, or safe and routed to the owner most likely to fix it. Slack, PagerDuty, email, or a webhook of your own.
Charge — required field renamed
payment_method → payment_method_id · detected 42s ago
#integrations
Slack · assigned Maya
pagerduty.com
P2 · routed
platform@acme.com
digest · daily
Every diff is scored. Breaking changes get paged. Additive changes slip quietly into the audit trail. Nothing in between wakes your on-call at 2am.
Any client calling this endpoint without the new field will 4xx in production.
schema Charge:properties:- payment_method: { required: true }+ payment_method_id: { required: true }
Still accepted today — scheduled for removal. Worth reviewing before the next release.
type SubscriptionStatus:- active- trialing- - unpaid # @deprecated+ - past_due
Additive, non-breaking change. Noted in the history so you always have the record.
schema Customer:properties:email: string+ preferred_locale?: string
Pick the path that matches your team. Mix and match across integrations — the baseline works the same way regardless.
Paste a public spec URL. We poll it on your schedule and alert when anything changes.
Drag in OpenAPI, GraphQL, or MCP manifests. Perfect for internal APIs and private providers.
Ship the spec on every merge. Baselines stay in lockstep with your deploys, not your polling window.
Same breaking change. Two very different stories depending on when you find out.
Reactive
Without Intello
Day 1
Silent change ships
Provider renames a required field. No one notices.
Day 14
Customer reports an error
Support ticket surfaces. Engineers start grepping.
Day 21
Fire-drill fix
Hotfix merged. Revenue and trust already taken a hit.
Proactive
With Intello
Hour 0
Intello detects the diff
Polling run catches the rename, classifies it breaking.
Hour 1
Right owner alerted
Slack + PagerDuty page the team that owns the integration.
Same day
Fix deployed
Patch ships before a single customer hits the bug.
Everything about spec formats, polling cadence, classification, and alert routing — in one place.
Contact usWe support OpenAPI (Swagger) 2.0 and 3.x, GraphQL introspection schemas, and Model Context Protocol (MCP) server manifests. You can provide specs via URL or direct upload.
Polling frequency depends on your plan: Free (12 hours), Starter (6 hours), Pro (1-3 hours), and Enterprise (custom intervals). Changes are detected and classified within minutes of polling.
Our AI analyzes each detected change and classifies it as safe (documentation updates, non-breaking additions), risky (behavioral changes, deprecations), or breaking (removed fields, changed types, new required parameters). This helps you prioritize what needs immediate attention.
Yes, you can upload spec files directly. This is useful for private APIs or when you want to compare against a specific version. You can also update uploaded specs manually or set up CI/CD integrations.
When a change is detected, you'll receive a notification via your configured channels (email, Slack). The alert includes what changed, the severity classification, and which of your dependencies might be affected.
We automatically retry failed fetches with exponential backoff. If a spec remains unavailable for multiple polling cycles, you'll receive an alert. Your historical data and previous spec versions are preserved.
Paste a spec, see the first diff the next time it changes. No agents, no infra, no credit card required.
