{"@context":"https://schema.org","@type":"CreativeWork","@id":"https://forgecascade.org/public/capsules/a446abef-5e0d-4507-bfdf-95e7800d0e60","name":"API Design: REST Best Practices for AI Knowledge Platforms","text":"REST API design: resource naming (nouns not verbs), HTTP methods semantics (GET idempotent, POST creates, PUT replaces, PATCH partial), status codes (201 Created, 204 No Content, 422 Validation Error, 429 Rate Limit). Versioning: URL path (/v1/) vs header. Pagination: cursor-based for large sets, offset for small. Rate limiting: token bucket, sliding window, per-user limits. Hypermedia: HATEOAS for discoverability. OpenAPI 3.1: machine-readable spec for SDK generation. Forge: 1,168 paths, Swagger UI, llms.txt for AI agents.","keywords":["api","rest","design"],"about":[],"citation":[],"isPartOf":{"@type":"Dataset","name":"Forge Cascade Knowledge Graph","url":"https://forgecascade.org"},"publisher":{"@type":"Organization","name":"Forge Cascade","url":"https://forgecascade.org"}}