mirror of
https://github.com/katanemo/plano.git
synced 2026-06-17 15:25:17 +02:00
Update README.md
This commit is contained in:
parent
6624e4efd9
commit
3fcb63d357
1 changed files with 4 additions and 4 deletions
|
|
@ -39,10 +39,10 @@ And you think to youself, can't I move faster by focusing on higher-level object
|
|||
**Core Features**:
|
||||
|
||||
- `Routing`. Engineered with purpose-built [LLMs](https://huggingface.co/collections/katanemo/arch-function-66f209a693ea8df14317ad68) for blazng fast (<100ms) routing and hand-off decisions to downstream agents.
|
||||
- `Fast ⚡ Function Calling`: For common agentic scenarios, expose tools as APIs and let Arch instantly clarify and convert prompts to structured APIs.
|
||||
- `Guardrails`: Centralizes guardrails to prevent jailbreak attempts and harmful outcomes, and ensure safe user interactions.
|
||||
- `Unified Access to LLMs`: Arch centralizes calls to LLMs, offering smart retries, automatic cutover, and resilient upstream connections for continuous availability.
|
||||
- `Observability`: Arch uses the W3C Trace Context standard to enable request tracing, ensuring compatibility with observability tools, and provides metrics to monitor latency, token usage, and error rates.
|
||||
- `Fast ⚡ Function Calling`: For common agentic scenarios let Arch clarfiy and convert prompts to tools and APIs.
|
||||
- `Guardrails`: Centrally configure and prevent jailbreaks and harmful outcomes, and ensure safe user interactions.
|
||||
- `Unified Access to LLMs`: Centralize= calls to LLMs with smart retries, automatic cutover, and resilient upstream connections for continuous availability.
|
||||
- `Observability`: W3C Trace Context compatiblerequest tracing, ensuring compatibility with popular observability tools, and provides metrics to monitor latency, token usage, and error rates.
|
||||
- `Built on Envoy`: Arch runs alongside application servers as a separate containerized process, and builds on top of [Envoy's](https://envoyproxy.io) proven HTTP management and scalability features to handle ingress and egress traffic related to prompts and LLMs.
|
||||
|
||||
**High-Level Sequence Diagram**:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue