Spreadsheet-safe CSV serializer
WHEN TO USE: Export scalar rows to CSV with RFC 4180 quoting and spreadsheet formula protection. By default, prefixes an apostrophe to string cells/headers beginning with =,+,-,@, their full-width variants, tab, CR, or LF (also after leading whitespace). Numeric values remain numeric; null becomes an empty cell. escapeFormulas=false is an explicit opt-out for trusted machine-only data; no escaping is universally safe after spreadsheet re-save. Optional unique headers; rectangular rows; CRLF and final newline by default. Maximum 1,000 rows, 100 columns, 100,000 output characters.
structured · Operation ID: csv-serialize
Choose this operation when
- Serialize scalar rows with default formula-trigger escaping.
Outside this profile
- A guarantee of safety after spreadsheet re-save or XLSX generation.
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": {
"rows": {
"maxItems": 1000,
"type": "array",
"items": {
"maxItems": 100,
"type": "array",
"items": {
"type": [
"string",
"number",
"boolean",
"null"
]
}
}
},
"headers": {
"minItems": 1,
"maxItems": 100,
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"maxLength": 2048
}
},
"delimiter": {
"default": ",",
"type": "string",
"enum": [
",",
";",
"\t",
"|"
]
},
"newline": {
"default": "crlf",
"type": "string",
"enum": [
"crlf",
"lf"
]
},
"finalNewline": {
"default": true,
"type": "boolean"
},
"escapeFormulas": {
"default": true,
"type": "boolean"
}
},
"required": [
"rows"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "csv-serialize",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"csv": {
"type": "string",
"maxLength": 100000
},
"rowCount": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"columnCount": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"escapedCells": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"csv",
"rowCount",
"columnCount",
"escapedCells"
],
"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
{
"headers": [
"customer",
"amount",
"comment"
],
"rows": [
[
"Ada",
49.5,
"paid"
],
[
"Lin",
20,
"=HYPERLINK(\"https://example.com\")"
]
]
}
Example response
{
"operation": "csv-serialize",
"version": "0.29.0",
"result": {
"csv": "customer,amount,comment\r\nAda,49.5,paid\r\nLin,20,\"'=HYPERLINK(\"\"https://example.com\"\")\"\r\n",
"rowCount": 2,
"columnCount": 3,
"escapedCells": 1
},
"provenance": {
"inputSha256": "3ac7682b1e2c885963261d2758d3a28f83e723047243636d594ae8ff781905b6",
"outputSha256": "1ebe7c7cde33757d848c02399325fab0eff66cdc158a9645d9bc8e9a66f5508a",
"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/csv-serialize",
"mpp": "/v1/mpp/csv-serialize"
}
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.