watasu
Agent-native encrypted intake rail

Publish a machine-readable request contract, receive encrypted submissions, and keep payload custody outside watasu.

Live intake routemetadata-only
01Request YAML

Agent-readable fields and consent text.

02Agent Card

Submit URL, schema hash, encryption params.

03Encrypted submit

watasu validates without plaintext custody.

04Receiver row

Private receiver decrypts and acts.

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.

No payload custody

watasu validates and forwards encrypted envelopes without receiving, decrypting, logging, or retaining plaintext payload values.

AI-readable docs

This site builds llms.txt and llms-full.txt so agents can discover the product, boundaries, and public surfaces without scraping repository internals.

End-to-end demo target

The target demo flow 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.