Terms of Service - Binary Transfer Lane for MCP (TextForAgents LLC)

- The product is provided by TextForAgents LLC to agent operators and MCP server operators whose workflows hand a binary file to a tool (receipts, screenshots, attachments, agent-generated artifacts); each customer is responsible for the files it transfers and for the accuracy of the (server identity, tool name, call id, declared mime/size/SHA-256) declaration it mints a transfer against.
- Service behavior is as stated in the product docs and in the pricing sheet; no promise beyond them is made. Stated plainly, because the lab proved the boundaries: (i) a delivery receipt is issued only when the arrived file's size and SHA-256 match the declaration bound to the tool call - a hash-mismatched or size-mismatched upload receives NO receipt (422) and the tool call cannot reference it; (ii) upload and download tokens are single-use and short-expiry - a second use, an expired token, or a receipt replayed against a different call id is refused; (iii) transfers above 1 GB are refused at mint; (iv) delivered objects are deleted on delivery and undelivered objects are deleted at expiry - the lane is a transfer service, not a storage service, and no retention beyond the transfer window is sold; (v) the lane covers agent-generated files with no human in the loop - it does not implement the draft SEP elicitation flows, which remain draft and unshipped; (vi) demand and willingness to pay for the call-bound lane itself are UNMEASURED at launch.
- Paid use is per transfer / per server-operator lane month as stated in the pricing sheet; the one-time trial grant (one free transfer per operator, ever) is exactly as stated there and does not renew. The server-operator lane covers a stated allowance (500 transfers + 50 GB per month) with transfers beyond the allowance metered at the per-transfer tiers, exactly as stated in the pricing sheet - no unlimited lane is sold.
- The service may be stopped via the kill switch; receipts already issued remain verifiable records under the retention term in the privacy policy; stopping never retroactively validates or invalidates a receipt. On stop, no new transfers are minted.
- Support: support@textforagents.com