Typed TOML configuration composer
Compose deterministic TOML 1.0-compatible configuration from explicit string, signed-int64, boolean and homogeneous-array declarations; preserve integer precision and detect table conflicts.
structured · Operation ID: toml-config-compose
Choose this operation when
- Creating new TOML 1.0-compatible files from explicit typed declarations
- Preserving full signed-int64 precision without JavaScript numeric conversion
- Producing an inert exact-byte configuration artifact for an offline consumer
Outside this profile
- Parsing, merging or editing existing TOML source or preserving comments
- Floating-point values, dates, times, null, nested or mixed arrays, arrays of tables or inline tables
- Application configuration validation, interpolation, environment expansion, filesystem includes or secret classification
- Network requests, writing files, live configuration changes, authentication, publishing or deployment
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": {
"tables": {
"maxItems": 128,
"type": "array",
"items": {
"type": "object",
"properties": {
"path": {
"maxItems": 4,
"type": "array",
"items": {
"type": "string",
"maxLength": 128
}
},
"entries": {
"maxItems": 512,
"type": "array",
"items": {
"type": "object",
"properties": {
"key": {
"type": "string",
"maxLength": 128
},
"value": {
"anyOf": [
{
"type": "object",
"properties": {
"type": {
"type": "string",
"const": "string"
},
"value": {
"type": "string",
"maxLength": 32768
}
},
"required": [
"type",
"value"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"type": {
"type": "string",
"const": "integer"
},
"value": {
"type": "string",
"maxLength": 20
}
},
"required": [
"type",
"value"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"type": {
"type": "string",
"const": "boolean"
},
"value": {
"type": "boolean"
}
},
"required": [
"type",
"value"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"type": {
"type": "string",
"const": "array"
},
"elementType": {
"type": "string",
"enum": [
"string",
"integer",
"boolean"
]
},
"values": {
"maxItems": 256,
"type": "array",
"items": {
"anyOf": [
{
"type": "string",
"maxLength": 32768
},
{
"type": "boolean"
}
]
}
}
},
"required": [
"type",
"elementType",
"values"
],
"additionalProperties": false
}
]
}
},
"required": [
"key",
"value"
],
"additionalProperties": false
}
}
},
"required": [
"path",
"entries"
],
"additionalProperties": false
}
}
},
"required": [
"tables"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "toml-config-compose",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"profile": {
"type": "string",
"const": "toml-1.0-typed-config-v1"
},
"text": {
"type": "string",
"maxLength": 100000
},
"byteLength": {
"type": "integer",
"minimum": 0,
"maximum": 100000
},
"sha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"tableCount": {
"type": "integer",
"minimum": 0,
"maximum": 128
},
"entryCount": {
"type": "integer",
"minimum": 0,
"maximum": 512
}
},
"required": [
"profile",
"text",
"byteLength",
"sha256",
"tableCount",
"entryCount"
],
"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
{
"tables": [
{
"path": [
"server"
],
"entries": [
{
"key": "port",
"value": {
"type": "integer",
"value": "8080"
}
},
{
"key": "enabled",
"value": {
"type": "boolean",
"value": true
}
},
{
"key": "name",
"value": {
"type": "string",
"value": "café"
}
}
]
}
]
}
Example response
{
"operation": "toml-config-compose",
"version": "0.29.0",
"result": {
"profile": "toml-1.0-typed-config-v1",
"text": "[\"server\"]\n\"enabled\" = true\n\"name\" = \"café\"\n\"port\" = 8080\n",
"byteLength": 59,
"sha256": "87bc7526e622cadc468e1870a97859ccc52909d2419e07064af6162e22a99d35",
"tableCount": 1,
"entryCount": 3
},
"provenance": {
"inputSha256": "fe94f7a66d0e2d6a9ea149fd1123d7e3673ab90b272e1a4b855a7683f273e4da",
"outputSha256": "050fb9b266805cf67ae8e4a0d458b3b89cd5424fe22ae1e866475934ef7d3f6f",
"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": 300000,
"jsonNodes": 12000,
"depth": 20,
"tables": 128,
"entries": 512,
"tablePathSegments": 4,
"keyUtf8Bytes": 128,
"arrayCells": 256,
"aggregateCells": 2048,
"stringValueUtf8Bytes": 32768,
"artifactUtf8Bytes": 100000,
"profile": "toml-1.0-typed-config-v1"
}
}
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/toml-config-compose",
"mpp": "/v1/mpp/toml-config-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.