
Why Rigid APIs Break Agents — and Email Doesn't
Strict API contracts turn small agent mistakes into hard failures. Email tolerates ambiguity, supports clarification, and keeps the whole exchange on the record.
Blog
Practical writing on productivity, AI, and building software.

Strict API contracts turn small agent mistakes into hard failures. Email tolerates ambiguity, supports clarification, and keeps the whole exchange on the record.

Pretraining freezes your model's worldview on a date that has already passed. We compare knowledge editing research with retrieval as strategies for keeping an AI assistant accurate.

When agents email agents, threads, signatures and pleasantries become expensive noise. Here's the case for a structured A2A email layer with provenance, intent tags, and evaluation built in.

Most agent failures aren't reasoning failures — they're broken context handoffs between tools, memory, and steps. Here's where the seams actually tear, and how to reinforce them.

REST contracts assume a developer read the docs. Agents haven't. Here's why MCP and A2A give AI agents the context-rich email interface they actually need.

The industry keeps drafting new agent-to-agent handshake specs. Meanwhile, email quietly ships addressable identity, async delivery, and threading — the interoperability layer AI agents already have.

Email is the messiest RAG corpus you'll ever ingest. Here are the chunking, dedup, and recency choices that make inbox retrieval trustworthy.

AI coding agents now write convincing 'task complete' reports the repository doesn't back up. Generation is cheap; verification is the real bottleneck.

The best production agents are boring: deterministic software that calls an LLM at a few deliberate points—not a chatbot with root access.

RAG over your email, docs, and spreadsheets usually fails at retrieval, not generation. Better search and chunking beat a bigger model almost every time.

The bottleneck in production AI agents isn't model IQ — it's context engineering, tool reliability, and memory. Here's what actually breaks and how to fix it.

Prototyping a workflow agent is easy. Running one in production is where auth, retries, evals, and oversight quietly eat your quarter. Here's how to decide.
Get started
Claim your address before someone else does — free to start, with an AI-native inbox built in.