A programming language for AI agents.

In Tin, the compiler checks what an agent may do — which tools it can reach, what needs a person's yes, and where a model's words may go — before the program runs. It is for developers who ship agents, and for the coding agents that write programs for them.

$ curl -fsSL https://tin.ad/install.sh | bash

Learn Tin Deploy an agent Why a language

From install to a live agent in under five seconds

Install, write a four-line agent, and tin deploy it. Every agent becomes a streaming HTTPS endpoint at its own name.tin.ad, with WebSocket, MCP and an EIP-8004 identity file (an Ethereum proposal for agent identity) beside it.

$ cat hello.tin
/// Says hello to whoever just deployed it.
agent Hello {
  model: "bedrock:us.anthropic.claude-haiku-4-5-20251001-v1:0"
  system: "Answer in one short, friendly sentence."
}
$ tin deploy hello.tin --yes
uploading hello.tin (3 KB) to https://api.tin.ad

live: https://eager-wombat-a7tp.tin.ad   anonymous, expires in 24 h (tin login keeps it)
$ curl -N https://eager-wombat-a7tp.tin.ad/agents/Hello \
    -H 'accept: text/event-stream' -d '{"prompt":"hi"}'
event: text
data: {"text":"…"}
…
event: done
data: {"text":"…","turns":1,"tokens":…}
Measured 16 November at 14:33Z on a second Mac with only Node 24 installed (the installer needs Node 24 or newer), in an empty home directory: 4.6 s from the install command to the end of a streamed Claude Haiku 4.5 answer, first byte after 0.44 s. Output abridged; the address is from an earlier run. --yes answers yes to the one question a deploy asks: whether to send your model key from the environment to this deployment's secret store. Without it, you are asked. No key? model: "mock" deploys and streams the same way. Without an account a deploy lasts 24 hours, 10 per address per day; tin login keeps it.

The compiler checks what an agent may do

Agent mistakes are not prompt problems; they are paths through a program. Tin finds those paths at compile time, so a tool that moves money two calls away from the agent still needs a person's approval:

error: tool 'pay' can run 'wire', which is guarded, without anyone approving it
 --> sneaky.tin:4:35
  = note: path: pay → payInvoice → wire
  = fix: mark pay as guarded

Why now

Models increasingly write and run code, and every product is becoming an endpoint that an agent talks to. Today that code is glue across four languages, and nothing checks what the agent is allowed to do. The ground under one language finally exists: WASI 0.2, isolates at the edge, and small native binaries run the same program from browser to server to device.

What is measured today

WhatResultSource
Install → streaming agent on tin.ad (Node 24+ present)4.6 stin.ad
Model providers written in Tin12; live on Claude Haiku 4.5 and gpt-oss-20b, the rest against recordingsproviders
Native hello binary107 KB, 4.4 ms to run — on par with Rust (343 KB, 4.3 ms)status
Recursive fib(36) on Node, median of 7Tin 53 ms · JS 99 · Python 667 · Rust 25bench
Where Tin loseson Node: agent loop 112 ms vs JS 72; also hello, mandelbrot, nbody, treesbench
Tin compiler written in Tinbyte-identical to the reference on 1,346 programs; rebuilds itself to the same bytesstatus

No users, customers or stars are claimed here. Everything still in progress is on /status.

Where it goes

Plan, not built yet: tin.ad becomes the place agents live — a signed name, a public identity through EIP-8004, and endpoints any other agent can find and call. The language makes those agents safe to let models write; the platform makes them one command to ship. If agents become a main way software is used, the place where they are named, checked and run is a business the size of web hosting. Read the memo.

Who builds it

Çağatay Çalı: on GitHub since 2014 with more than 450 public repositories, author of fastify/benchmarks, and working on agent frameworks and on agents that drive real robots. He directs coding agents in parallel lanes, and a critic agent that never edits the code must pass each one. About

Start

Learn Tin Deploy Playground