You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/openapi.json
+16-2Lines changed: 16 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4447,7 +4447,7 @@
4447
4447
],
4448
4448
"summary": "Handle A2A Jsonrpc",
4449
4449
"description": "Handle A2A JSON-RPC requests following the A2A protocol specification.\n\nThis endpoint uses the DefaultRequestHandler from the A2A SDK to handle\nall JSON-RPC requests including message/send, message/stream, etc.\n\nThe A2A SDK application is created per-request to include authentication\ncontext while still leveraging FastAPI's authorization middleware.\n\nAutomatically detects streaming requests (message/stream JSON-RPC method)\nand returns a StreamingResponse to enable real-time chunk delivery.\n\nArgs:\n request: FastAPI request object\n auth: Authentication tuple\n mcp_headers: MCP headers for context propagation\n\nReturns:\n JSON-RPC response or streaming response",
4450
-
"operationId": "handle_a2a_jsonrpc_a2a_get",
4450
+
"operationId": "handle_a2a_jsonrpc_a2a_post",
4451
4451
"responses": {
4452
4452
"200": {
4453
4453
"description": "Successful Response",
@@ -4465,7 +4465,7 @@
4465
4465
],
4466
4466
"summary": "Handle A2A Jsonrpc",
4467
4467
"description": "Handle A2A JSON-RPC requests following the A2A protocol specification.\n\nThis endpoint uses the DefaultRequestHandler from the A2A SDK to handle\nall JSON-RPC requests including message/send, message/stream, etc.\n\nThe A2A SDK application is created per-request to include authentication\ncontext while still leveraging FastAPI's authorization middleware.\n\nAutomatically detects streaming requests (message/stream JSON-RPC method)\nand returns a StreamingResponse to enable real-time chunk delivery.\n\nArgs:\n request: FastAPI request object\n auth: Authentication tuple\n mcp_headers: MCP headers for context propagation\n\nReturns:\n JSON-RPC response or streaming response",
4468
-
"operationId": "handle_a2a_jsonrpc_a2a_get",
4468
+
"operationId": "handle_a2a_jsonrpc_a2a_post",
4469
4469
"responses": {
4470
4470
"200": {
4471
4471
"description": "Successful Response",
@@ -7343,6 +7343,14 @@
7343
7343
"title": "Authorization headers",
7344
7344
"description": "Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header. To specify this use a string 'client' instead of the file path. 3. Usage of the oauth token in the header. To specify this use a string 'oauth' instead of the file path. "
7345
7345
},
7346
+
"headers": {
7347
+
"items": {
7348
+
"type": "string"
7349
+
},
7350
+
"type": "array",
7351
+
"title": "Propagated headers",
7352
+
"description": "List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS."
| authorization_headers | object | Headers to send to the MCP server. The map contains the header name and the path to a file containing the header value (secret). There are 3 special cases: 1. Usage of the kubernetes token in the header. To specify this use a string 'kubernetes' instead of the file path. 2. Usage of the client-provided token in the header. To specify this use a string 'client' instead of the file path. 3. Usage of the oauth token in the header. To specify this use a string 'oauth' instead of the file path. |
4825
+
| headers | array | List of HTTP header names to automatically forward from the incoming request to this MCP server. Headers listed here are extracted from the original client request and included when calling the MCP server. This is useful when infrastructure components (e.g. API gateways) inject headers that MCP servers need, such as x-rh-identity in HCC. Header matching is case-insensitive. These headers are additive with authorization_headers and MCP-HEADERS. |
4748
4826
| timeout || Timeout in seconds for requests to the MCP server. If not specified, the default timeout from Llama Stack will be used. Note: This field is reserved for future use when Llama Stack adds timeout support. |
4749
4827
4750
4828
@@ -5454,6 +5532,47 @@ Example:
5454
5532
| status | object | The status of the service |
5455
5533
5456
5534
5535
+
## StreamingInterruptRequest
5536
+
5537
+
5538
+
Model representing a request to interrupt an active streaming query.
5539
+
5540
+
Attributes:
5541
+
request_id: Unique ID of the active streaming request to interrupt.
5542
+
5543
+
5544
+
| Field | Type | Description |
5545
+
|-------|------|-------------|
5546
+
| request_id | string | The active streaming request ID to interrupt |
5547
+
5548
+
5549
+
## StreamingInterruptResponse
5550
+
5551
+
5552
+
Model representing a response to a streaming interrupt request.
5553
+
5554
+
Attributes:
5555
+
request_id: The streaming request ID targeted by the interrupt call.
5556
+
interrupted: Whether an in-progress stream was interrupted.
5557
+
message: Human-readable interruption status message.
0 commit comments