Available · v1

Scope Intelligence

Send your statement of work, deliverables, exclusions, assumptions, and amendments, with a new request. Get back whether it's in scope, excluded, or needs a change request, quoting the agreement language that applies.

  • Every reference quotes your agreement exactly
  • Explicit exclusions and assumptions surfaced
  • Approved amendments taken into account
  • Ambiguity returns uncertain, never a guess
Try it in the playgroundAPI reference
Request body
{
  "statement_of_work": "Contoso will redesign and build the customer portal for Fabrikam, including account management and order history pages.",
  "deliverables": [
    "Responsive web portal with login, account settings, and order history",
    "Integration with Fabrikam's existing order API",
    "Two rounds of design revisions"
  ],
  "exclusions": [
    "Native mobile applications",
    "Data migration from the legacy portal"
  ],
  "assumptions": [
    "Fabrikam provides API documentation and a staging environment",
    "English-language content only"
  ],
  "requested_change": "Can you also build iOS and Android apps with the same features?"
}
Response · 200 OK
{
  "request_id": "req_Np2wK7rTx4LmQ9vB",
  "status": "requires_change_request",
  "recommended_action": "initiate_change_request",
  "applicable_requirements": [],
  "potential_conflicts": [
    {
      "text": "Native mobile applications",
      "source": "exclusions[0]",
      "relation": "excludes"
    }
  ],
  "new_deliverable": true,
  "missing_information": [
    "acceptance_criteria"
  ]
}
The problem

Scope creep starts with "can you also…"

Delivery teams field new requests every week. Deciding whether each one is already covered, excluded, or billable means rereading the agreement, and inconsistent answers cost margin or goodwill.

Item-by-item check
Each deliverable, acceptance criterion, amendment, exclusion, and assumption is evaluated against the request separately.
Clear outcomes
Within scope, potentially out of scope, requires a change request, or uncertain, with the next step.
Traceable
Applicable requirements and conflicts quote your agreement with the field they came from.
Use cases

Where teams use it

  • Professional services
  • Change management
  • Project delivery
  • Agency client requests
  • Implementation partners
Integrate

One HTTP call

const response = await fetch("https://kovca.io/api/v1/scope/check", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.KOVCA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "statement_of_work": "Contoso will redesign and build the customer portal for Fabrikam, including account management and order history pages.",
    "deliverables": [
      "Responsive web portal with login, account settings, and order history",
      "Integration with Fabrikam's existing order API",
      "Two rounds of design revisions"
    ],
    "exclusions": [
      "Native mobile applications",
      "Data migration from the legacy portal"
    ],
    "assumptions": [
      "Fabrikam provides API documentation and a staging environment",
      "English-language content only"
    ],
    "requested_change": "Can you also build iOS and Android apps with the same features?"
  }),
});

if (!response.ok) {
  const { error, request_id } = await response.json();
  throw new Error(`${error.code}: ${error.message} (${request_id})`);
}

const { status, recommended_action, potential_conflicts } = await response.json();

Related APIs

  • Policy Evaluation

    Check requests against the policies you write and get a structured, advisory decision.

  • Data Quality Intelligence

    Find missing values, contradictions, and semantic inconsistencies in structured business records.

  • Content Intelligence

    Evaluate user-generated content against your platform rules and get a structured moderation recommendation.