Protocol

Protocol

Core request and response structure

---

Request Format

A Mesh request is a JSON object with the following structure:

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": "req_abc123",
  "call": {
    "function": "service.action",
    "version": "1",
    "arguments": { }
  },
  "context": { },
  "extensions": [ ]
}

Top-Level Fields

Field	Type	Required	Description
protocol	string	Yes	Protocol identifier and version. MUST use format: mesh/<major>.<minor>
id	string	Yes	Unique request identifier. MUST correlate request to response.
call	object	Yes	The function invocation details
context	object	No	Propagated metadata. See Context.
extensions	array	No	Extension objects with urn and options. See Extensions.

Call Object

The call object specifies what function to invoke:

Field	Type	Required	Description
function	string	Yes	Function identifier MUST use <service>.<action> format
version	string	No	Function version. Defaults to latest. See Versioning.
arguments	object	No	Function arguments. Defaults to empty object {} if omitted.

ID Field

The id field uniquely identifies a request attempt.

Type: String only. Implementations SHOULD use one of:

• UUID v4: "550e8400-e29b-41d4-a716-446655440000"
• Prefixed random: "req_abc123xyz"
• ULID: "01ARZ3NDEKTSV4RRFFQ69G5FAV"

The id field MUST NOT be:

• Null
• Empty string
• Numeric (to avoid JSON precision issues)
• An object or array

Function Naming

Function names MUST use dot notation: <service>.<action>

Examples:

• orders.create
• users.get
• inventory.reserve

Function names beginning with mesh. are reserved. See System Functions.

Function names are case-sensitive. Implementations SHOULD use lowercase with underscores for multi-word actions: orders.get_by_customer.

---

Response Format

A Mesh response is a JSON object with the following structure:

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": "req_abc123",
  "result": { },
  "meta": { }
}

Top-Level Fields

Field	Type	Required	Description
protocol	string	Yes	Protocol identifier and version
id	string	Yes	Echoed from request. MUST correlate response to request.
result	any	Conditional	Function return value. MUST be present on success.
errors	array	Conditional	Array of error objects. Present when request fails.
meta	object	No	Response metadata
async	object	No	Async operation status. See Async.

Result Field

On success, result contains the function’s return value. The type depends on the function:

• Object: { "order_id": 123 }
• Array: [{ "id": 1 }, { "id": 2 }]
• Scalar: 42, "ok", true
• Null: When function returns nothing

On error, result MUST be null.

Error Fields

A response MUST contain exactly one of:

• result with value (success)
• errors with array of error objects (failure)

On error, result MUST be null. The errors array MUST contain at least one error.

See Errors for error object structure.

Meta Object

OPTIONAL metadata about the response:

Field	Type	Description
node	string	Identifier of the server node that handled the request
rate_limit	object	Rate limit status. See Rate Limiting.

Note: Server-side processing duration is provided via the Tracing Extension.

Rate Limit Object

{
  "rate_limit": {
    "limit": 1000,
    "used": 153,
    "remaining": 847,
    "window": { "value": 1, "unit": "minute" },
    "resets_in": { "value": 45, "unit": "second" }
  }
}

See Rate Limiting for full specification.

Implementations MAY add additional fields to meta.

---

Parse Errors

When a request cannot be parsed as valid JSON:

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": null,
  "result": null,
  "errors": [
    {
      "code": "PARSE_ERROR",
      "message": "Invalid JSON: unexpected end of input",
      "retryable": false,
      "source": {
        "position": 52
      }
    }
  ]
}

The id field MUST be null when the request’s id could not be determined.

The source.position field SHOULD contain the byte offset where parsing failed, if available.

---

Transport Conventions

HTTP

When using HTTP transport:

Aspect	Convention
Method	MUST use POST
Content-Type	MUST be application/json
Endpoint	Service-defined (e.g., /mesh, /rpc)
HTTP Status	MUST use 200 for all Mesh responses

HTTP status codes SHOULD NOT indicate Mesh-level errors. Use the error/errors field.

Exception: Transport-level errors (502, 503, 504) indicate the request never reached the Mesh handler.

Message Queues

When using message queue transport:

Aspect	Convention
Message format	MUST be JSON-encoded Mesh request
Correlation	MUST use message correlation ID matching Mesh id
Reply queue	SHOULD specify in message properties

---

Examples

Minimal Request

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": "req_001",
  "call": {
    "function": "health.check",
    "version": "1"
  }
}

Minimal Response

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": "req_001",
  "result": { "status": "healthy" }
}

Full Request

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": "req_xyz789",
  "call": {
    "function": "orders.create",
    "version": "2",
    "arguments": {
      "customer_id": 42,
      "items": [
        { "sku": "WIDGET-01", "quantity": 2 }
      ]
    }
  },
  "context": {
    "trace_id": "tr_8f3a2b1c",
    "span_id": "sp_4d5e6f",
    "parent_span_id": "sp_1a2b3c",
    "caller": "checkout-service"
  },
  "extensions": [
    {
      "urn": "urn:mesh:ext:deadline",
      "options": { "value": 5, "unit": "second" }
    }
  ]
}

Full Response

{
  "protocol": { "name": "mesh", "version": "0.1.0" },
  "id": "req_xyz789",
  "result": {
    "order_id": 12345,
    "status": "pending",
    "created_at": "2024-01-15T10:30:00Z"
  },
  "meta": {
    "node": "orders-api-2"
  }
}