# LLMs.txt: integrate with AI > Download the Signclad integration docs and API schema as plain text for your AI assistant. Source: https://signclad.com/docs/llms/ Give your AI assistant the documentation it needs to build a Signclad integration. The downloads are generated from these guides and the published API schema on every site build. ## Download the docs - Download the guides pack (.txt) — every prose guide in one file, without the schema. Start here: it is an order of magnitude smaller than the full pack, and it is the half an assistant actually reads. - Download the full integration guide (.txt) — the same guides plus the complete OpenAPI schema. Large, and mostly specification, so reach for it when your assistant has the context window and needs exact field shapes inline. - Download llms.txt — a short index: the four downloads with their measured sizes, then every guide with a link to its Markdown version. Use this with an assistant that can fetch URLs, or to let it pick a file it can hold. - Download the OpenAPI schema (.yaml) — every published operation, request, response, and error schema. The same document is at /openapi/signclad.v1.json for tools that only read JSON. Both packs cover authentication, creating and sending documents, templates, text tags, embedded signing and builders, webhook delivery and verification, errors, rate limits, test mode, migration, the compatibility reference, and MCP. The sizes in `llms.txt` are measured from the files that build emitted, so they cannot drift from what you download. ## A starter prompt Attach the full integration guide, then describe your application and the workflow you need: ```text Help me integrate Signclad into my application using the attached documentation. My stack is [language and framework]. I want to [describe the document workflow and recipients]. Use the included OpenAPI schema for exact endpoints and request fields. Start with a sandbox key stored server-side in an environment variable. Use recipient addresses I control: test mode sends real emails. Add idempotency keys, error handling, and verified webhook processing. Never include API keys in browser code, logs, or the conversation. Ask about missing requirements instead of inventing API capabilities. Explain how to test the integration before switching to a live key. ``` ## Before you start API and MCP access require Light or above. Create a sandbox key in your workspace's API settings and keep it in your application's secret store. Share the documentation with your assistant, not your credentials or private documents. Test documents send real emails with a test notice and carry a watermark stating that they are not legally binding. They do not count toward billable usage. Use addresses you control while developing. No Signclad client library is published to npm, so `npm install` will not find one and an assistant that writes `import { createClient } from '@signclad/sdk'` is writing against something you cannot install. Call the API over plain HTTP, or generate a client from the OpenAPI schema — which is what the schema is there for. ## Smaller context windows Start with [llms.txt](https://signclad.com/llms.txt), then load only the Markdown guides relevant to your workflow and the API schema. Each guide has a plain Markdown version at `/docs/markdown/{guide-name}.md`, such as [Getting started](https://signclad.com/docs/markdown/getting-started.md). Links inside the downloads are rewritten to absolute URLs, so they still resolve once the file is outside the website. Downloaded files are snapshots. Download a fresh copy when revisiting an integration. For an assistant that should operate on documents directly, see the [MCP integration guide](https://signclad.com/docs/mcp/).