tin.ad
Deploy a Tin program and get a URL. No account, no config file.
$ tin deploy app.tin
uploading app.tin (14 KB) to https://api.tin.ad
live: https://brisk-otter-k3m9.tin.ad anonymous, expires in 24 h
The tin command line is not publicly installable yet; this page describes what runs today.
What you get
- A name like
brisk-otter-k3m9.tin.ad, served over HTTPS. - For each agent in the file, an EIP-8004 registration file at
/agents/<Name>/registration.jsonand the domain file at/.well-known/agent-registration.json. Registering on a chain is opt-in and on test networks only (tin register). tin ls,tin logs,tin rm,tin secrets set NAME.
How it is kept apart
- Each deployment runs in its own isolate, created with only its own secrets.
- Secrets are encrypted at rest under a key bound to the deployment's name.
tin deployasks before it sends a key from your environment, and refuses long-lived cloud access keys. - You upload the compiled program only. tin.ad runs its own copy of the Tin runtime around it, so the compiler's checks (capabilities, approvals, taint) are the ones that ran.
- Deployments cannot call tin.ad itself, plain http, or private addresses.
Limits, for anonymous deploys
| lifetime | 24 hours |
| deploys | 10 per address per day |
| requests | 1000 per deployment per day, 60 per minute per address |
| size | 6 MB per upload |
| pages | served with Content-Security-Policy: sandbox: no scripts, no forms |
Sign-in (to keep a deployment and pick its name) is not open yet.
Report abuse
curl -X POST https://api.tin.ad/v1/abuse -d '{"url":"https://name.tin.ad/","reason":"phishing"}'
A person reads every report.