René's URL Explorer Experiment

  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What is an OpenAPI diff?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "An OpenAPI diff (or differential) is the result of comparing two versions of an OpenAPI specification to identify all the changes between them. Unlike a simple text diff, a proper OpenAPI diff tool understands the structure and semantics of the specification. It can pinpoint specific changes like a removed endpoint, a modified data type, or a new required parameter, and classify them as breaking or non-breaking."
        }
      },
      {
        "@type": "Question",
        "name": "How do I compare two OpenAPI specs?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "You can compare two OpenAPI specs using a specialized tool like CodeRifts. You can use our free in-browser tool by simply uploading your two specification files. For a more automated workflow, you can integrate our GitHub App to get a comparison on every pull request, or use our CLI or REST API to run a comparison in your own scripts or CI/CD pipelines."
        }
      },
      {
        "@type": "Question",
        "name": "What counts as a breaking change?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "A breaking change is any modification to an API contract that can cause existing client applications to fail. Common examples include removing an endpoint, adding a new required request parameter, removing a field from a response, or changing the data type of a field. CodeRifts maintains a comprehensive list of over 10 common breaking change types that it detects automatically."
        }
      },
      {
        "@type": "Question",
        "name": "Does CodeRifts support OpenAPI 3.1?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes, CodeRifts has full support for OpenAPI 3.1, as well as OpenAPI 3.0 and OpenAPI 2.0 (formerly known as Swagger). Our diff engine is designed to handle the nuances and features of each version, including the latest additions in 3.1 like webhooks and improved JSON Schema compatibility."
        }
      },
      {
        "@type": "Question",
        "name": "Can I use this in CI/CD?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Absolutely. Integrating API diffing into your CI/CD pipeline is a best practice for preventing breaking changes from reaching production. CodeRifts provides both a CLI tool and a REST API that you can easily incorporate into your existing workflows, whether you use Jenkins, GitLab CI, CircleCI, or any other automation server. You can configure your pipeline to fail a build if a high-risk breaking change is detected."
        }
      },
      {
        "@type": "Question",
        "name": "Can I diff OpenAPI specs without an API key?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. The in-browser tool at app.coderifts.com/try requires no signup, and the zero-auth endpoint POST /api/v1/demo returns a full diff verdict with no API key, which is useful for quick checks and for AI agents. For higher-volume or authenticated use, the REST API uses a free API key (1,000 requests per month free)."
        }
      },
      {
        "@type": "Question",
        "name": "How is CodeRifts different from oasdiff or the openapi-diff CLI?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "oasdiff (a Go CLI by Tufin) and the openapi-diff npm and Java tools produce a raw structural diff and a breaking or non-breaking classification, which is excellent for CI pipelines you assemble yourself. CodeRifts adds a governance layer on top of the diff: a 0 to 100 risk score, policy enforcement, OWASP-aligned security analysis, an auto-generated changelog, and zero-config delivery as a GitHub App PR comment. Use a raw diff tool if you only need the delta; use CodeRifts if you need a decision about whether the change is safe to ship."
        }
      },
      {
        "@type": "Question",
        "name": "Can an AI agent diff OpenAPI specs before acting on them?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. CodeRifts serves a full diff verdict over a zero-auth endpoint (POST /api/v1/demo), and a zero-dependency coderifts_guard decorator turns that verdict into a one-line guardrail for LangGraph, AutoGen, or any Python agent. If a change would break a downstream contract, the agent halts before the unsafe call runs. Reference implementation: github.com/coderifts/example-langgraph-guard."
        }
      },
      {
        "@type": "Question",
        "name": "Can I connect CodeRifts to Claude or Cursor via MCP?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. CodeRifts runs as a hosted MCP server at https://app.coderifts.com/mcp (Streamable HTTP). Add it to Claude Desktop, Cursor, or any MCP client and the agent can diff OpenAPI specs, score breaking-change risk, and get an ALLOW, WARN, REQUIRE_APPROVAL, or BLOCK decision before merging or before a tool call. The one-click connect page and full tool list are at https://coderifts.com/for-agents."
        }
      },
      {
        "@type": "Question",
        "name": "What MCP tools does CodeRifts provide?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "CodeRifts exposes eight governance tools over MCP, including preflight_check (diff an API spec change and return risk, blast radius, incident cost, and a merge decision), mcp_diff (compare two MCP manifests for breaking changes), and agent_tool_check (detect whether an API change breaks AI agent tool calling). Each returns the same Decision Spec v1.0 envelope, so an agent can branch on a stable contract. Full list and connect config: https://coderifts.com/for-agents."
        }
      }
    ]
  }