<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Meshi Engineering Web Log</title><link>https://meshi.io/blog</link><description>Engineering notes, experiments, and technical decisions from Meshi.</description><language>en</language><item><title>JSON or XML for tool calls? It depends on the model, and on how you read the reply</title><link>https://meshi.io/blog/json-or-xml-for-tool-calls</link><description>We planned 1,440 stateful tool-calling workflows across three models, crossing the format a model writes with the format its environment speaks back. No format came out ahead everywhere; the write-read interaction mattered more, and for one model, parse failures traced to how our client read multi-message replies dominated the result.</description><guid isPermaLink="true">https://meshi.io/blog/json-or-xml-for-tool-calls</guid><pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate></item><item><title>From Ascend to Meshi: what we kept, what we rebuilt</title><link>https://meshi.io/blog/ascend-became-meshi</link><description>Tracing the Ascend-to-Meshi product lineage through portable identity, evidence, and the distinction between a brand change and a platform rebuild.</description><guid isPermaLink="true">https://meshi.io/blog/ascend-became-meshi</guid><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Headless by design: the agent, not another destination</title><link>https://meshi.io/blog/headless-by-design</link><description>A retrospective on Meshi’s agent-first turn: why text and voice became the conversation, what the web kept, and why deleting a chat window was only the beginning.</description><guid isPermaLink="true">https://meshi.io/blog/headless-by-design</guid><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Meshi meets MCP: a small interface to a personal network</title><link>https://meshi.io/blog/meshi-meets-mcp</link><description>A retrospective on Meshi&apos;s first public MCP beta: three read-only tools, account-scoped access, and the design work between an internal tool server and a useful external integration.</description><guid isPermaLink="true">https://meshi.io/blog/meshi-meets-mcp</guid><pubDate>Sat, 24 Oct 2026 00:00:00 GMT</pubDate></item><item><title>A small model that goes first: triaging LinkedIn matches before the LLM</title><link>https://meshi.io/blog/small-model-goes-first</link><description>We trained a 150M-parameter encoder to judge LinkedIn identity matches ahead of Gemini 3.1 Flash Lite. Alone it matched fewer people than Gemini. Going first, with Gemini deciding whenever the encoder was unsure, it matched more people on two held-out development sets, lost none that Gemini got right, and cut Gemini spend by about 60% in replay.</description><guid isPermaLink="true">https://meshi.io/blog/small-model-goes-first</guid><pubDate>Wed, 21 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Reordering event matches with an LLM nearly doubled the good ones in the top ten</title><link>https://meshi.io/blog/llm-rerank-event-matches</link><description>At one event, the order of the top ten was where match quality was lost. An LLM reading short profile cards for 50 candidates nearly doubled the good matches in the top ten, a check without grader labels agreed, and a two-step version kept most of the gain at about $1.25 per 1,000 searches.</description><guid isPermaLink="true">https://meshi.io/blog/llm-rerank-event-matches</guid><pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Which search API actually finds the right person? We ran 3,800 queries to find out</title><link>https://meshi.io/blog/which-search-api-finds-the-right-person</link><description>We benchmarked Google (through two SERP vendors), Exa, Parallel and Tavily on turning a name and an employer into one exact LinkedIn profile. Exa&apos;s people search and Google tied near 90%, and for people we believed had no findable profile every engine usually handed back someone else.</description><guid isPermaLink="true">https://meshi.io/blog/which-search-api-finds-the-right-person</guid><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate></item></channel></rss>