Most Rust frameworks force you to choose: Speed (Actix) OR Ergonomics (Axum). RustAPI gives you both.
We built the framework we wanted: FastAPI's developer experience backed by Rust's raw performance. No boilerplate. No fighting the borrow checker for simple handlers. Just code that flies.
Problem: Standard JSON APIs are verbose and expensive for Large Language Models (LLMs). Solution: RustAPI natively supports TOON (Token-Oriented Object Notation).
Top-tier LLMs (Claude, GPT-4) charge by the token. RustAPI's TOON format reduces response token counts by 50-58% compared to standard JSON.
- 💰 Save 50% on API Costs: Half the tokens, same data.
- 🌊 Zero-Latency Streaming: Built for real-time AI agents.
- 🔌 MCP-Ready: Out-of-the-box support for Model Context Protocol.
"RustAPI isn't just a web server; it's the native language of your AI agents."
We optimize for Developer Joy without sacrificing Req/Sec.
| Feature | RustAPI | Actix-web | Axum | FastAPI (Python) |
|---|---|---|---|---|
| Performance | ~92k req/s | ~105k | ~100k | ~12k |
| DX (Simplicity) | 🟢 High | 🔴 Low | 🟡 Medium | 🟢 High |
| Boilerplate | Zero | High | Medium | Zero |
| AI/LLM Native | ✅ Yes | ❌ No | ❌ No | ❌ No |
| Stability Logic | 🛡️ Facade | ✅ Stable |
Write your API in 5 lines. It's that simple.
use rustapi_rs::prelude::*;
#[derive(Serialize, Schema)]
struct Message { text: String }
#[rustapi::get("/hello/{name}")]
async fn hello(Path(name): Path<String>) -> Json<Message> {
Json(Message { text: format!("Hello, {}!", name) })
}
#[rustapi::main]
async fn main() {
// 1 line to rule them all: Auto-discovery, OpenAPI, Validation
RustApi::auto().run("127.0.0.1:8080").await
}That's it. You get:
- ✅ Swagger UI at
/docs - ✅ Input Validation
- ✅ Multi-threaded Runtime
- ✅ Zero Config
We build in public. Here is our immediate focus for February 2026:
- Visual Status Page: Automatic health dashboard for all endpoints.
- gRPC Integration: First-class support via Tonic.
- Distributed Tracing: One-line OpenTelemetry setup.
- RustAPI Cloud: One-click deploy to major cloud providers.
We moved our detailed architecture, recipes, and deep-dives to the Cookbook.
