Upload your OpenAPI, Postman, or GraphQL spec. Get the same change detection, severity scoring, and alert routing we ship for prebuilt integrations.
First spec free forever. OpenAPI, Postman, GraphQL, MCP.
OpenAPI 2.0 and 3.x. Postman collections. GraphQL introspection. MCP server manifests. Paste a URL, drop a file, or push from CI on every deploy.
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.
One platform for the integrations we prebuilt, the ones your team built, and everything in between.
The auth API. The billing service. The thing your team rewrote last sprint. Watch every internal spec on every deploy.
Private vendors, NDA partners, and one-off integrations without an official catalog entry. Pull with auth headers or push from CI.
Anything in the long tail we haven't prebuilt yet. If it has a spec, we can monitor it. Same engine, same alerts.
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
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.
Skip the upload. Toggle on a prebuilt integration and start getting alerts in the next minute.
Spec formats, syncing with deploys, staging vs production, authentication, and how to start.
Contact usOpenAPI (Swagger) 2.0 and 3.x, Postman collections, GraphQL introspection schemas, and Model Context Protocol (MCP) server manifests.
Three options. Poll a public URL on a schedule. Upload a file. Or push from your CI/CD pipeline on every release. Most teams pick CI push for internal services.
Yes. Each spec is its own monitored integration with its own baseline and routing rules. Run staging on PR, prod on release.
Pull from a private URL with auth headers, or push from CI. Specs are stored in your tenant only. We diff and discard the payload.
Free covers one spec. Paid plans scale by spec count and polling cadence. See pricing for the full breakdown.
Start with the catalog at /integrations. We've already done the work for hundreds of vendors. Use Custom APIs for whatever it doesn't cover.
OpenAPI, Postman, GraphQL, MCP. Upload once and watch every change land scored, routed, and ready.
