openapi

A set of rules for documenting a Rust web API with OpenAPI, a standard format for describing API endpoints and data. It uses the utoipa library and keeps the generated documentation behind an optional openapi feature.

In plain words
What is it for?
Adding documented routes and data schemas, registering them centrally, and generating an OpenAPI 3.1 description for an Axum application.
Why use it?
It keeps API documentation consistent with the code and avoids including its extra dependencies in production builds unless needed. It also sets expectations for examples, names, and error responses.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/saynaai/sayna/openapi
Clone the repo
git clone --depth 1 https://github.com/SaynaAI/sayna

Made for: Cursor.

Per session 5,255 This file is loaded in full into every session.
When invoked 5,255 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.05255 $0.05255
Opus 5 $0.02627 $0.02627
Sonnet 5 $0.01051 $0.01051
Haiku 4.5 $0.00526 $0.00526

Measured 2d ago against content hash 1a2808a33674, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openapi scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/openapi.mdc · 790 lines

How it starts

The opening of the file, as written. The whole thing — 790 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenAPI Documentation Guidelines

This document provides comprehensive guidelines for writing OpenAPI annotations in the Sayna Rust/Axum codebase using the utoipa crate.

Overview

Sayna uses utoipa (v5.3+, latest is v5.4) for OpenAPI 3.1 specification generation. All OpenAPI-related code is feature-gated behind the openapi feature flag to keep dependencies minimal in production builds.

Key Principles

  1. Feature-Gated: All OpenAPI code must be conditionally compiled with #[cfg_attr(feature = "openapi", ...)]
  2. Centralized Documentation: All paths, schemas, and tags are registered in src/docs/openapi.rs
  3. Complete Examples: Every field should have meaningful examples that reflect real-world usage
  4. Consistent Style: Follow established patterns for naming, descriptions, and error responses
  5. Type Safety: Leverage Rust's type system to ensure documentation matches implementation

Feature Flag Setup

Cargo.toml Configuration

[features]
openapi = [
    "dep:utoipa",
]

[dependencies]
utoipa = { version = "5.3", optional = true, features = ["axum_extras"] }

# Optional: For more ergonomic route registration
# utoipa-axum = { version = "0.2", optional = true }

Optional: Enhanced Axum Integration

Consider adding utoipa-axum for more ergonomic route registration:

use utoipa_axum::{routes, router::OpenApiRouter};

let (router, api) = OpenApiRouter::new()
    .routes(routes!(health_check, list_voices, speak_handler))
    .split_for_parts();

Running with OpenAPI

# Run server with OpenAPI endpoints
cargo run --features openapi

# Generate OpenAPI spec to file
cargo run --features openapi -- openapi -o docs/openapi.yaml

# Generate JSON format
cargo run --features openapi -- openapi --format json -o docs/openapi.json

Schema Annotations

Basic Schema Definition

Use #[cfg_attr(feature = "openapi", derive(utoipa::ToSchema))] on all types exposed in the API:

use serde::{Deserialize, Serialize};

/// Health check response
#[derive(Debug, Serialize, Deserialize)]
#[cfg_attr(feature = "openapi", derive(utoipa::ToSchema))]
pub struct HealthResponse {
    /// Server status
    #[cfg_attr(feature = "openapi", schema(example = "OK"))]
    pub status: String,
}

Read the full file on GitHub · 790 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 790 lines · 5,255 tokens per session scan A 1a2808a33674

Subscribe to this mod's changes

openapi is a cursor rule published in the GitHub repository SaynaAI/sayna (311 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 5,255 tokens to every session, about $0.0263 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.