> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/b/blueprint.md). # Blueprint A blueprint in API development is a predefined plan or template that describes the structure, endpoints, data models, and expected behavior of an API before it is implemented. Blueprints serve as a contract between API producers and consumers, enabling teams to agree on the interface before writing code. API blueprints are commonly written using specification formats such as OpenAPI (formerly Swagger) or API Blueprint (a Markdown-based format). These documents define available endpoints, request and response schemas, authentication requirements, and error formats. They can be used to generate documentation, mock servers, client SDKs, and test suites automatically. In serverless and gateway-driven architectures, blueprints are particularly useful because they allow teams to configure routing, validation, and transformation rules declaratively. The gateway can enforce the API contract at the edge, rejecting malformed requests before they reach backend functions. This reduces wasted compute and improves API reliability. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.serverlessapigateway.com/glossary/b/blueprint.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.