# ask.imeatsack.com > An agent asks. A human answers. Create a questionnaire, paste the link, wait. No install, no setup, no dashboard to learn. ask.imeatsack.com is how an agent asks a human a set of questions. Create returns an answer link and a private manage link. The human answers in the browser. The agent can inspect or edit while nobody has answered, then wait, poll, or be called back. MCP and HTTP are the same questionnaire. ## I, Meatsack family - [I, Meatsack](https://imeatsack.com): Ask, Share and Show. - [Ask](https://ask.imeatsack.com/llms.txt): Questionnaires for human input. - [Share](https://share.imeatsack.com/llms.txt): Send and request files. - [Show](https://show.imeatsack.com/llms.txt): Publish pages and workbooks. ## Docs - [Homepage in Markdown](https://ask.imeatsack.com/index.md): Product overview and family navigation. - [Complete documentation](https://ask.imeatsack.com/llms-full.txt): Overview, installation, skill and API guide. - [Install plugin](https://ask.imeatsack.com/install): Marketplace setup for Codex, Claude Code, and Cursor - [Skill](https://ask.imeatsack.com/skill.md): How to use the ask.imeatsack.com tool - [MCP and HTTP](https://ask.imeatsack.com/mcp.md): Connect, actions, curl, machine answering - [Plugin marketplace](https://github.com/garylesueur/meatsack-marketplace): Install in Codex, Claude Code, or Cursor - [Plugin source](https://github.com/garylesueur/askmeatsack): MCP plus the skill - [Home](https://ask.imeatsack.com/): Human landing page ## Optional - [llms.txt](https://ask.imeatsack.com/llms.txt) ## Answer a questionnaire for your user If your user gives you an answer link, fetch that same URL with `Accept: text/markdown` or append `.md` to the path before its query string, keeping the `t` token. The document includes every question, saved answers, status, expiry, and JSON Schema. Send all answers in one `PUT /api/v1/sessions/{sessionId}/answers?t=…` with `Content-Type: application/json` and `{"answers": {"questionId": {"text": "Your answer"}}, "submit": true}`. Use the exact URL, question ids, option ids, and answer shapes from the document. Confirm `submitted.status` is `submitted`. No account, API key, MCP installation, or browser clicks are needed to answer. Ask your user for missing information rather than inventing answers. The answer link is private; do not publish it in an index.