# Documents larger than the input gate What the input ceiling applies to, and which formats stay readable when a document is larger than the gate. The input ceiling applies to the document, not to the answer, and it is a property of one string rather than of the transport: The input ceiling is memory on one string, not a limit on the answer: a 50M-character document is about 100MB in UTF-16 inside an isolate that holds 128MB, so the gate is how large the document is. It does not shrink the response and is not a transport limit - a 60MB document refused by the gate would have been a far smaller answer. Above the gate, formats that can be addressed by parts are read as parts and the document is never materialized at all (the table above says which); for the ones that cannot, nothing lifts it: `part` selects inside a document that has already been built, and streaming frames the answer without making the document smaller. Whether a large resource can still be read at all is a property of its format, and it is decided before the first byte is fetched: | Formats | Above the input gate | Why | | ------------------------------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DOCX, XLSX, XLSM, XLSB, PPTX, ODT, ODS, ODP, EPUB | By the extension alone | The text of a package is a few small entries while the bulk is media nobody needs for extraction, so the document is read entry by entry and stays reachable whole - with or without `part` | | PDF | By the extension alone | The cross-reference table maps every object to an absolute offset, so text streams are read directly and image streams skipped - reachable whole, with or without `part` | | ZIP, TAR, 7z | With `part` or `result=meta` | The index sits in the tail (a ZIP's central directory, a 7z's index behind its signature header; a TAR's headers ARE its index), so the inventory is read from the tail alone, without the bulk, and any one entry can be fetched as a slice. Without `part` the whole book is the answer, and building it needs every byte | | GZ, XZ, LZMA, BZ2, ZST and `.tar.*` | Not addressable | Sequential formats with no tail index: a record is reachable only after everything before it has been decompressed, so the input gate stands | | DOC, XLS, PPT (legacy binary office) | Not addressable | These are OLE2/CFB containers with no ZIP index, so there is nothing to seek with and the input gate stands | | File mode (data URI) | Not addressable | The bytes are already in the request body, which has no ranges to address; the gate applies to the decoded payload | ## Links - **About service:** https://mdapi.io/about - **API documentation and conversion:** https://mdapi.io - **MCP server manifest:** https://mdapi.io/mcp - **Health check:** https://mdapi.io/health - **Documentation index:** https://mdapi.io/llms.txt - **Full API documentation:** https://mdapi.io/llms-full.txt - **AI discovery:** https://mdapi.io/.well-known/ai-discovery.json or https://mdapi.io/ai-discovery.json - **AI Agent discovery:** https://mdapi.io/.well-known/agent.json or https://mdapi.io/agent.json - **A2A Agent card:** https://mdapi.io/.well-known/agent-card.json or https://mdapi.io/agent-card.json - **ACP manifest:** https://mdapi.io/.well-known/acp.json or https://mdapi.io/acp.json - **x402 payment manifest:** https://mdapi.io/.well-known/x402.json or https://mdapi.io/x402.json - **OpenAPI specification (JSON):** https://mdapi.io/.well-known/openapi.json or https://mdapi.io/openapi.json - **OpenAPI specification (YAML):** https://mdapi.io/.well-known/openapi.yaml or https://mdapi.io/openapi.yaml - **MAPI specification:** https://mdapi.io/.well-known/mapi.md or https://mdapi.io/mapi.md - **Skill specification:** https://mdapi.io/.well-known/skill.md or https://mdapi.io/skill.md - **Agent Plugins manifest:** https://mdapi.io/.well-known/plugin/plugin.json or https://mdapi.io/.well-known/plugin.json - **Agent Plugins MCP config:** https://mdapi.io/.well-known/plugin/mcp.json - **Agent Plugins conversion skill:** https://mdapi.io/.well-known/plugin/skills/mdapi-conversion/SKILL.md - **API documentation pages:** https://mdapi.io/docs ## External Links - **github.com** https://github.com/mdapiio/mdapi.io - **skills.sh** https://www.skills.sh/mdapiio/mdapi.io - **skillsmp.com** https://skillsmp.com/creators/mdapiio/mdapi.io - **clawhub.ai** https://clawhub.ai/mdapiio - **x.com** https://x.com/mdapiio ## Disclaimer **The service is provided "AS IS".** > mdapi.io is an edge-native service-transport primitive for AI, autonomous-agents, and the Web4 ecosystem.