91-api-routes

91-api-routes is a cursor rule for Cursor from zoxknez/ai-coding-rules. It costs 0 tokens per session (819 once invoked), scanned A, original, MIT.

Coding rules for API routes, the server-side endpoints that receive requests and return data. They apply automatically to files in `api` or `routes` folders and cover validation, errors, and route structure.

In plain words
What is it for?
Use them when creating or updating endpoints, such as user routes. They guide Zod input checks, HTTP status codes, authentication and rate-limiting middleware, and shared response types.
Why use it?
They reduce bugs caused by unchecked input and inconsistent responses. They also keep endpoint code organized across common Next.js projects.

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/zoxknez/ai-coding-rules/91-api-routes
Clone the repo
git clone --depth 1 https://github.com/zoxknez/ai-coding-rules

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for 91-api-routes

README.md
[![agentmods](https://agentmods.dev/badge/rules/zoxknez/ai-coding-rules/91-api-routes.svg)](https://agentmods.dev/rules/zoxknez/ai-coding-rules/91-api-routes)
Your own site
<a href="https://agentmods.dev/rules/zoxknez/ai-coding-rules/91-api-routes"><img src="https://agentmods.dev/badge/rules/zoxknez/ai-coding-rules/91-api-routes.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 819 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00819
Opus 5 $0.00000 $0.00409
Sonnet 5 $0.00000 $0.00164
Haiku 4.5 $0.00000 $0.00082

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

Security

Grade A, and why

91-api-routes 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/91-api-routes.mdc · 138 lines

How it starts

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

🔌 API Routes Rules

Auto-activated for files in /api/ or /routes/ directories.

Route Structure

api/
├── users/
│   ├── route.ts          # Next.js App Router
│   ├── [id]/route.ts     # Dynamic route
│   └── schema.ts         # Zod validation
├── middleware.ts         # Auth, rate limiting
└── types.ts              # Shared types

Rules

1. Input Validation (STRICT)

// ✅ ALWAYS validate all inputs
import { z } from 'zod';

const CreateUserSchema = z.object({
  email: z.string().email(),
  name: z.string().min(2).max(100),
  age: z.number().int().positive().optional(),
});

export async function POST(request: Request) {
  const body = await request.json();
  const result = CreateUserSchema.safeParse(body);
  
  if (!result.success) {
    return Response.json({ error: result.error.flatten() }, { status: 400 });
  }
  
  // Use result.data (validated)
}

2. Error Handling (STRICT)

// ✅ Consistent error envelope
interface ApiResponse<T> {
  data?: T;
  error?: {
    code: string;
    message: string;
    details?: unknown;
  };
}

// ✅ Proper status codes
// 200 - Success
// 201 - Created
// 400 - Bad Request (validation failed)
// 401 - Unauthorized
// 403 - Forbidden
// 404 - Not Found
// 500 - Internal Server Error

3. Authentication (STRICT)

// ✅ ALWAYS check auth before processing
export async function GET(request: Request) {
  const session = await getServerSession(authOptions);
  
  if (!session) {
    return Response.json({ error: { code: 'UNAUTHORIZED' } }, { status: 401 });
  }
  
  // Check authorization (permissions)
  if (!hasPermission(session.user, 'users:read')) {
    return Response.json({ error: { code: 'FORBIDDEN' } }, { status: 403 });
  }
  
  // Process request...
}

4. Rate Limiting

// ✅ Apply rate limiting for public endpoints
import { rateLimit } from '@/lib/rate-limit';

const limiter = rateLimit({
  interval: 60 * 1000, // 1 minute
  uniqueTokenPerInterval: 500,
});

export async function POST(request: Request) {
  try {
    await limiter.check(5, 'API_ROUTE_NAME'); // 5 requests per minute
  } catch {
    return Response.json({ error: { code: 'RATE_LIMITED' } }, { status: 429 });
  }
}

Read the full file on GitHub · 138 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. 4d ago First seen · 138 lines · 0 tokens per session scan A d5a8783c1c18

Subscribe to this mod's changes

91-api-routes is a cursor rule published in the GitHub repository zoxknez/ai-coding-rules (28 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 819 tokens. 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.