Diff bounded line sequences
Use for auditable changes between small documents. Computes a minimal insertion/deletion script by bounded longest-common-subsequence, with one-based old/new line numbers; ties delete first. Maximum 300 lines and 30,000 UTF-16 units per document. Compares line content exactly but ignores CR/LF separator style; a final newline is an additional empty line. Not a byte diff, patch file, or fuzzy diff.
text · Operation ID: lines-diff
Choose this operation when
- Inspect exact bounded line changes with source line numbers.
Outside this profile
- Large files, fuzzy matching, byte comparison, or executable patch output.
Exact release references
Static JSON contract · Markdown reference · Fixed example response
Complete input schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"before": {
"type": "string",
"maxLength": 30000
},
"after": {
"type": "string",
"maxLength": 30000
}
},
"required": [
"before",
"after"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "lines-diff",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"equal": {
"type": "boolean"
},
"beforeLines": {
"type": "integer",
"minimum": 0,
"maximum": 300
},
"afterLines": {
"type": "integer",
"minimum": 0,
"maximum": 300
},
"inserted": {
"type": "integer",
"minimum": 0,
"maximum": 300
},
"deleted": {
"type": "integer",
"minimum": 0,
"maximum": 300
},
"unchanged": {
"type": "integer",
"minimum": 0,
"maximum": 300
},
"operations": {
"maxItems": 600,
"type": "array",
"items": {
"type": "object",
"properties": {
"kind": {
"type": "string",
"enum": [
"equal",
"delete",
"insert"
]
},
"text": {
"type": "string",
"maxLength": 30000
},
"oldLine": {
"anyOf": [
{
"type": "integer",
"minimum": 1,
"maximum": 300
},
{
"type": "null"
}
]
},
"newLine": {
"anyOf": [
{
"type": "integer",
"minimum": 1,
"maximum": 300
},
{
"type": "null"
}
]
}
},
"required": [
"kind",
"text",
"oldLine",
"newLine"
],
"additionalProperties": false
}
}
},
"required": [
"equal",
"beforeLines",
"afterLines",
"inserted",
"deleted",
"unchanged",
"operations"
],
"additionalProperties": false
},
"provenance": {
"type": "object",
"required": [
"inputSha256",
"outputSha256",
"deterministic",
"externalRequests"
],
"properties": {
"inputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"outputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"deterministic": {
"const": true
},
"externalRequests": {
"const": 0
}
}
}
},
"additionalProperties": false
}
Fixed example
One accepted fixed example, not a custom-input trial. No operation runs when this static page is requested.
Example input
{
"before": "status: pending\nowner: agent",
"after": "status: ready\nowner: agent\nverified: yes"
}
Example response
{
"operation": "lines-diff",
"version": "0.29.0",
"result": {
"equal": false,
"beforeLines": 2,
"afterLines": 3,
"inserted": 2,
"deleted": 1,
"unchanged": 1,
"operations": [
{
"kind": "delete",
"text": "status: pending",
"oldLine": 1,
"newLine": null
},
{
"kind": "insert",
"text": "status: ready",
"oldLine": null,
"newLine": 1
},
{
"kind": "equal",
"text": "owner: agent",
"oldLine": 2,
"newLine": 2
},
{
"kind": "insert",
"text": "verified: yes",
"oldLine": null,
"newLine": 3
}
]
},
"provenance": {
"inputSha256": "068d2614e67a7711f69ba149a0078057a3d513739d4cd29472e862844c79cf7e",
"outputSha256": "12f9ddb453a70083094c4adc8a8fa2a5961c67eb609a6f53a7db12c8d8d35d24",
"deterministic": true,
"externalRequests": 0
}
}
Bounds and precision
JavaScript IEEE-754 numbers; use strings for large integer IDs/exact decimals where the schema accepts strings. No lossless numeric parsing.
{
"global": {
"requestBytes": 131072,
"responseBytes": 524288,
"jsonDepth": 32,
"jsonNodes": 20000,
"requestsPerMinute": 60,
"paidAttemptsPerMinute": 20,
"idempotencyHours": 24
},
"operation": {
"requestBytes": 131072,
"responseBytes": 524288,
"jsonDepth": 32
}
}
Complete schemas, descriptions and cross-field validation may impose additional limits.
Proposed price and protocol definitions
{
"unit": "one successful operation call",
"proposedNominalUsd": "0.005",
"sixDecimalTokenBaseUnits": "5000",
"subscription": false,
"includesPayerWalletOrNetworkFees": false,
"liveQuoteVerified": false,
"condition": "Actual SDK challenge is authoritative only within the caller's explicit authorization; configured six-decimal token peg is an operator assertion, not a conversion guarantee."
}
Protocol definitions: x402, mpp. MPP uses Tempo charge. Paid MCP execution is unsupported. All runtime readiness is not evaluated in this build.
API path templates, not endpoints on this documentation host
{
"x402": "/v1/x402/lines-diff",
"mpp": "/v1/mpp/lines-diff"
}
Required headers
{
"Content-Type": "application/json",
"Idempotency-Key": "random 16–128 character operation identifier"
}
Actual SDK challenge amount, asset, network, recipient and wallet costs must pass independent authorization. Preserve identical key, body, protocol and credential on retries; on PAYMENT_UNCERTAIN stop and reconcile.
Execution profile and provider conditions
{
"deterministic": true,
"externalRequests": 0,
"maxExternalRequests": 0,
"resultSnapshotPersisted": false,
"fixedExampleIsIllustrativeSnapshot": false,
"requiresPayment": true,
"supportsMcpExecution": false
}
Deterministic supplied-input operation with no external requests or stored request/result bodies. Payment infrastructure retains payment metadata and hashes.
Failure handling
- HTTP 400: Malformed JSON, missing/invalid idempotency key, or payment identifier mismatch Correct the request before payment
- HTTP 402: Payment challenge or rejected payment Use official protocol SDK; inspect payment outcome before another payment
- HTTP 409: Idempotency conflict, duplicate proof, or PAYMENT_UNCERTAIN Keep original key, body, and proof; reconcile uncertainty with operator; never blindly repay
- HTTP 413: Input or generated output too large Reduce input; no payment attempted for validation failure
- HTTP 415: Unsupported media type or compression Send uncompressed application/json
- HTTP 422: Schema or service-specific semantic validation failure Correct input using returned error code; no payment attempted
- HTTP 429: Request/payment-attempt rate exceeded Wait for rate limit window; preserve existing payment identity
- HTTP 503: Payment configuration/provider/state unavailable, or live DNS preparation failed before settlement Check readiness; DNS preparation failures may retry the identical key/body/credential only; uncertainty requires reconciliation
Declared requirements
Before any paid call, refresh the live operation contract and POST the complete bounded budgeted plan to the separate API's /preflight. Unknown requirements block selection; compatible preflight is not permission to spend.