Literal-cell GFM table composer
WHEN TO USE: Turn an explicit rectangular string matrix into a paste-ready GitHub Flavored Markdown table with exact literal-cell escaping and supplied column alignments. Escapes every ASCII punctuation character, preserving cell text in the declared GFM profile. ASCII @ is rejected to prevent GFM email autolinks. No raw Markdown, HTML, links, newline substitution, display-width padding or non-GFM rendering guarantee.
structured · Operation ID: gfm-table-compose
Choose this operation when
- Compose paste-ready literal-cell GFM tables from supplied rows
- Serialize a rectangular string matrix as Markdown with explicit column alignments
Outside this profile
- ASCII @ or email-address cells; GFM email autolinking cannot be suppressed with punctuation escapes
- Parsing tables, CSV conversion, raw Markdown or HTML cells, links, code spans or multiline cells
- Pixel alignment, display-width padding or exact behavior on non-GFM renderers; browsers may collapse repeated spaces
- Sending, uploading, extracting archives, writing files, authenticating identities, or changing external state
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": {
"headers": {
"minItems": 1,
"maxItems": 20,
"type": "array",
"items": {
"type": "string",
"maxLength": 400,
"description": "Literal GFM cell: at most 200 Unicode scalars; no controls, leading/trailing ASCII spaces or ASCII @ (email autolinking cannot otherwise be suppressed)."
}
},
"align": {
"minItems": 1,
"maxItems": 20,
"type": "array",
"items": {
"type": "string",
"enum": [
"left",
"center",
"right"
]
}
},
"rows": {
"maxItems": 100,
"type": "array",
"items": {
"minItems": 1,
"maxItems": 20,
"type": "array",
"items": {
"type": "string",
"maxLength": 400,
"description": "Literal GFM cell: at most 200 Unicode scalars; no controls, leading/trailing ASCII spaces or ASCII @ (email autolinking cannot otherwise be suppressed)."
}
}
}
},
"required": [
"headers",
"align",
"rows"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "gfm-table-compose",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"markdown": {
"type": "string",
"maxLength": 50000
},
"rowCount": {
"type": "integer",
"minimum": 0,
"maximum": 100
},
"columnCount": {
"type": "integer",
"minimum": 1,
"maximum": 20
},
"byteLength": {
"type": "integer",
"minimum": 1,
"maximum": 50000
}
},
"required": [
"markdown",
"rowCount",
"columnCount",
"byteLength"
],
"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": [
"Name",
"Note"
],
"align": [
"left",
"right"
],
"rows": [
[
"A|B",
"<b>"
]
]
}
Example response
{
"operation": "gfm-table-compose",
"version": "0.29.0",
"result": {
"markdown": "| Name | Note |\n| :--- | ---: |\n| A\\|B | \\<b\\> |\n",
"rowCount": 1,
"columnCount": 2,
"byteLength": 49
},
"provenance": {
"inputSha256": "bd997c57f922649cb03ae151e68001c13b51aab9d7837893267028102ddd8e84",
"outputSha256": "371771ed09a9e61e0fb6a7bf77671979eefd5af875495834ddcd0608ef42c070",
"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": {
"inputBytes": 100000,
"outputBytes": 400000,
"jsonNodes": 12000,
"depth": 20,
"profile": "gfm-literal-table-v1",
"columns": 20,
"rows": 100,
"cellScalars": 200,
"aggregateCellBytes": 20000,
"atSign": "rejected to prevent unavoidable GFM email autolinking",
"renderedSpaces": "browser layout may collapse repeated spaces"
}
}
Complete schemas, descriptions and cross-field validation may impose additional limits.
Proposed price and protocol definitions
{
"unit": "one successful operation call",
"proposedNominalUsd": "0.003",
"sixDecimalTokenBaseUnits": "3000",
"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/gfm-table-compose",
"mpp": "/v1/mpp/gfm-table-compose"
}
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.