Posts

Meet FreeToken: An Edge-Native MoE Serving Engine that Runs 753B GLM-5.2 on a Single Workstation GPU

Frontier open-weight models are shipping faster than the hardware assumptions around them. Kimi-K3 , GLM-5.2 and DeepSeek-V4-Flash are closing the capability gap with proprietary systems, but releasing parameters only determines who can obtain a model — not who can afford to run it. Serving them still assumes datacenter-class GPU clusters, and as agentic workloads push inference demand up, that cost lands hardest on individual developers and small teams. Meanwhile, more than a hundred million consumer machines already carry discrete GPUs. A team of researchers from UC Berkeley and UT Austin propose FreeToken . The research team argued the missing piece is not hardware but a serving system: it treats a personal machine as a unified, elastic inference platform rather than a small GPU, and continuously maps computation and model state onto whatever GPU, CPU, memory and interconnect bandwidth the machine actually has. The result is a 35B model at interactive speed on an 8 GB laptop GP...

Vercel Introduces ‘Is Agentic’, a Free Agent-Readiness Scoring Tool That Audits Public Websites Using Ora’s 100+ Checks

Vercel has released Is Agentic , a public tool that scores how readily AI agents can discover, access, understand, and use a website. Scans are run and scored by Ora , an agent-experience research company from era labs. Vercel operates the interface, report pages, storage, and the grouping that produces the displayed score. Is it deployable? Yes — at zero cost. Is Agentic is currently free , with no paid plans, subscription charges, or per-report fees. The public site, read-only API, CLI, and MCP server require no API key or billing account. Enter a URL in the browser, or run the CLI: Copy Code Copied Use a different Browser npx is-agentic <domain> npx is-agentic <domain> --json Which level of company : Any organization owning a public web surface. Seed-stage startups get a free baseline audit with no procurement. Mid-market SaaS teams can wire --json output into CI as a regression gate. Enterprises can benchmark documentation portals, developer sites, ...

The Developer’s Guide to NeMo Guardrails for Enterprise AI Safety

In this tutorial, we build an in-depth NeMo Guardrails pipeline that demonstrates how layered guardrails can control an LLM-based financial assistant across the full request lifecycle. We combine deterministic PII detection and redaction, LLM-based input and output self-checks, retrieval filtering, account-number masking, topical restrictions, and policy-based tool gating. We also implement stateful multi-turn interactions, detailed rail activation tracing, token accounting, and a red-team-style coverage report, so we can evaluate whether the assistant responds safely, which control handles each request, and what computational cost that protection adds. Copy Code Copied Use a different Browser !pip install -q nemoguardrails import os, re, json, getpass, textwrap from typing import Optional MODEL = "gpt-4o-mini" BASE_URL = "" if not os.environ.get("OPENAI_API_KEY"): os.environ["OPENAI_API_KEY"] = getpass.getpass("API key: ") _ba...

Decoding AI’s Open-Source Course Maps Three Ways to Run an Agent Loop and the Provider Economics Behind Each

Most teams treat ‘which model’ as the important decision. The harness engineering literature keeps pointing somewhere else. In LangChain’s Terminal-Bench experiment , changing only the harness—same model throughout—moved a coding agent from roughly 30th place into the top 5. That result reframes the question. If the harness decides quality, then how you run the loop becomes an architecture decision, not a deployment detail. Paul Iusztin’s open-source course Building a Coding Agent From Scratch builds a Python agent called Decode . Published through Decoding AI , it separates three run modes. Each mode has a different latency profile. Each one therefore wants a different inference provider. One headless core, three shapes The center of the system is a headless harness with no interface of its own. Inside it runs the agent loop every harness shares: the LLM picks an action, a tool executes, the observation feeds back. Everything reads from and write...