Kami v1.12 is a quiet one. No new templates, no new looks, just a version you can trust more.
It now plans a document before laying it out, changes only the part you asked to fix and leaves approved pages alone, tells you honestly what it checked and what it skipped, and never lets a failed build overwrite your last working PDF.
ONE POSTER AFTER ANOTHER 😤
GG Jackson with the SLAM.
Victor Wembanyama with the RESPONSE.
As we celebrate the best 2025-26 slams during NBA Dunk Week, we had to bring back this classic dunk-off from March!
PLANTING HIS FLAGG 🏁
It's NBA Dunk Week, and @Cooper_Flagg claimed his spot as one of the game's top dunkers during his Kia NBA Rookie of the Year campaign!
Every gun, mine, and guard tower on the Berlin Wall was pointed at East Germans.
In 1957, the communist regime in East Germany made unauthorized emigration treason after an estimated 2.5 million people voted with their feet, fleeing the communist East towards the West.
So in 1961, the authorities closed the border, called the wall “the Anti-Fascist Protection Rampart”, and gave border guards shoot to kill orders.
People only ever risked their lives escaping in one direction.
Every API call gives you a choice: wait for the result now, or collect it later.
Agentic Document Extraction (ADE) works both ways when you run a Parse or Extract.
The first way is synchronous. You send the request and wait on the line until the result comes back. Simple, and right when someone needs the answer immediately.
The second is asynchronous. You submit the work, get a ticket, and pick up the result once it is done. Nothing sits waiting on an open line.
The result is identical either way. Same Markdown from Parse, same fields from Extract. You are only choosing how long you wait.
So why ever hand it off? Two reasons.
Big jobs need it. A single asynchronous Parse Job takes files up to 1 GB or 6,000 pages, far more than one live request can hold.
It also costs less. Waiting on the line runs at the top rate, since something is blocked on it. Hand the job off and you drop to a cheaper tier for the same result.
The rule of thumb is one question. If a person or an agent is waiting on the answer, run it synchronously. If nothing is waiting, submit a job and pay less.
Full breakdown, plus the service tier companion, in the comments.
Introducing Kitesurf: a browser built for agents, running entirely on Cloudflare Workers.
Chromium is too heavy to hand every agent one. Kitesurf is written in Rust, uses 3-7x less CPU and memory, and spins up per request.
Free in beta:
@Andercot You’re right, but one step at a time. Next step is extending consciousness permanently beyond Earth ideally during this civilizational up cycle, rather than than some far future one.