Demo
The sample raises issues from read to write.
The verdict below is computed by the same evaluator as POST /evaluate.
Verdict: review_required
Contract
{
"contractVersion": "1",
"integration": "toolpolicylint-demo",
"before": {
"tools": [
{
"name": "issues",
"permissions": [
"read"
]
},
{
"name": "contents",
"permissions": [
"read"
]
}
]
},
"after": {
"tools": [
{
"name": "issues",
"permissions": [
"write"
]
},
{
"name": "contents",
"permissions": [
"read"
]
}
]
}
}
Evidence
{
"contractVersion": "1",
"policyVersion": "1",
"integration": "toolpolicylint-demo",
"verdict": "review_required",
"summary": "Review required: 1 added permission(s) expand write/admin capability.",
"counts": {
"added": 1,
"removed": 1,
"reviewRequired": 1,
"unknown": 0
},
"changes": [
{
"kind": "tool_permission",
"change": "added",
"target": "write",
"class": "write",
"reviewRequired": true,
"unknown": false,
"reason": "added write permission (matched \"write\") requires review",
"tool": "issues"
},
{
"kind": "tool_permission",
"change": "removed",
"target": "read",
"class": "read",
"reviewRequired": false,
"unknown": false,
"reason": "removed read permission (reduction, no review)",
"tool": "issues"
}
],
"drivers": [
"issues: added write -> added write permission (matched \"write\") requires review"
]
}
Lint your own contract
POST /toolpolicylint/lint accepts the v1 contract JSON and
returns the evidence report. It shares the evaluate rate limit. When Stripe
billing is enforced, the route returns 402 until a Pro entitlement exists.
curl -s -X POST https://scopechange.dev/toolpolicylint/lint \
-H 'content-type: application/json' \
-d @CONTRACT.json
Stripe
Paid hosted lint uses the existing scopechange Pro checkout. No new Stripe
price is created here. Until owner keys are set, checkout answers
billing_disabled and does not charge a card.