Machine-readable intake
Request definitions, JSON Schema, Agent Cards, and A2A-compatible submit routes describe what is needed before a user-side agent sends data.
Publish a machine-readable request contract, receive encrypted submissions, and keep payload custody outside watasu.
Paste this as-is into your coding or operations agent. The agent should ask one compact four-slot question, then summarize and wait for confirmation before it publishes anything.
I want to use watasu to collect information from people through encrypted intake.
Use https://docs.watasu.ai/llms.txt and
https://docs.watasu.ai/operator-prompts.md only as watasu reference docs.
Do not plan web research, SEO, or llms.txt setup for my site.
Ask one compact setup question that covers exactly these slots: what to collect
and from whom, destination, purpose, and retention.A person starts from a natural-language request, not developer setup.
Docs, llms files, schemas, and Agent Cards ground the workflow.
Encrypted submissions are validated without plaintext custody.
The receiver owns decryption, destination writes, and obligations.
Request definitions, JSON Schema, Agent Cards, and A2A-compatible submit routes describe what is needed before a user-side agent sends data.
watasu validates and forwards encrypted envelopes without receiving, decrypting, logging, or retaining plaintext payload values.
This site builds llms.txt and llms-full.txt so agents can discover the product, boundaries, and public surfaces.
A good trial starts with a natural-language request and ends with a receiver-owned CSV or Sheet row, while watasu keeps plaintext payload custody out of scope.