Fix README

This commit is contained in:
Tao Chen
2026-04-20 17:54:44 -07:00
Unverified
parent cd48c1424c
commit 8b77baf4a2
3 changed files with 3 additions and 3 deletions
@@ -22,7 +22,7 @@ curl -X POST http://localhost:8088/invocations -i -H "Content-Type: application/
The server will respond with a JSON object containing the response text. The `-i` flag in the `curl` command includes the HTTP response headers in the output, which includes the session ID that can be used for multi-turn conversations. Here is an example of the response:
```
```bash
HTTP/1.1 200
content-length: 34
content-type: application/json
@@ -22,7 +22,7 @@ curl -X POST http://localhost:8088/invocations -i -H "Content-Type: application/
The server will respond with a JSON object containing the response text. The `-i` flag in the `curl` command includes the HTTP response headers in the output, which includes the session ID that can be used for multi-turn conversations. Here is an example of the response:
```
```bash
HTTP/1.1 200
content-length: 34
content-type: application/json
@@ -5,4 +5,4 @@ This folder contains a list of samples that show how to host agents using the `i
| Sample | Description |
| --- | --- |
| [01_basic](./01_basic) | A basic example of hosting an agent with the `invocations` API and carrying on a multi-turn conversation. |
| [02_break_glass](./02-break-glass) | An example of hosting an agent with the `invocations` API and a "break glass" scenario where you can create your own `invoke_handler` to handle specific types of invocations. |
| [02_break_glass](./02_break_glass) | An example of hosting an agent with the `invocations` API and a "break glass" scenario where you can create your own `invoke_handler` to handle specific types of invocations. |