Insights
Insights
What KINTO has learned building agentic systems, written as answers to concrete questions and grounded in published case studies.
Insights
- LatestCommerce and growth
How to reconcile what ad platforms report with your real orders
To reconcile ad-platform reports with real sales, match each order to its true source and measure every channel's return against the same cash, not against each platform's own attribution. In one KINTO case, one channel returned about twice the other. - ERP and operations
What is an agentic ERP, and why does it start read-only?
An agentic ERP is an AI layer on top of a company's ERP that reads its data, explains what is missing and proposes actions. It starts read-only because a wrong write to the books costs far more than a slow answer; writes to an existing ERP need a person's approval. - GEO
What is GEO, and how is kinto.co built so AI assistants cite it?
GEO (generative engine optimization) is structuring a website so AI assistants can understand, trust and cite it. KINTO built kinto.co with Kinto Studio to ship llms.txt, llms-full.txt, ai.txt, an AI-crawler allow-list, a sitemap with hreflang, JSON-LD and IndexNow. - Commerce and growth
How to migrate a WooCommerce store to headless without losing URLs
To migrate a WooCommerce store to headless without losing SEO, inventory every URL before touching anything, keep the same paths wherever possible, 301-redirect the rest, and measure page weight before and after. KINTO kept about 98% of one store's URLs on the same path. - AI agents
How to turn years of WhatsApp chats into knowledge an agent can trust
To turn years of WhatsApp conversations into knowledge an AI agent can trust, classify them with a closed taxonomy, transcribe voice notes, and admit a fact only if it appears in at least two distinct, recent conversations. - AI agents
Why a WhatsApp AI agent should not memorize your catalog
A WhatsApp AI agent should not memorize the catalog because memory goes stale and models fill gaps with plausible inventions. It should look up products, stock and prices in the system of record, and let code compute dates and totals.
Have a problem like this?
Tell KINTO what is going on. The first conversation is to understand it, not to sell.