The Machine Door: our whole agency, readable in one fetch.
Soon — sooner than most expect — the first visitor to most business websites will not be a human. It will be an AI agent researching on a human's behalf. We stopped waiting. As of today, an agent can read everything about SynapseIN in a single request. It's live, right now, at the address below.
Live now
Open the real file → (it's not a sample — that's the door itself)
Why a JSON file is a bigger deal than it looks
Today, when an AI assistant is asked "find me an SEO agency that works with clinics and won't fake its numbers," it reads websites the hard way: parsing prose, guessing at pricing, inferring trustworthiness from tone. Most of what it concludes is reconstruction.
The Machine Door removes the guessing. An agent that fetches one URL gets our identity, services, price ranges, verifiable claims and a documented way to contact us on its human's behalf — all typed, all parseable, no interpretation required. The agency becomes actionable to machines, not just visible to them.
And because every claim in the file carries its own verification link and a real date, an agent that checks claims — which is where all of this is heading — finds ours check out. That is the entire strategy: be the easiest agency in the world for a machine to verify.
How it fits with what already exists
Four layers, from permission to action. Almost every website on Earth stops at layer one.
Want one for your business?
Building a Machine Door properly is harder than it looks. The file format is the easy part — the hard part is what goes inside it: claims that survive verification, an engagement protocol that actually works, and the discipline to keep every date real. Get any of that wrong and a machine-checkable file exposes you faster than prose ever would.
We build Machine Doors for clients as part of our GEO work — wired into your llms.txt, your schema, and your actual proof. Ask us about it — it starts with a conversation, not a template.
Questions people ask
What is the Machine Door?
A single machine-readable file — synapsein.com/api/agency.json — that contains the entire agency in structured form: identity, services, pricing ranges, claims with verification links, refusal policies, and exactly how an AI agent can start a conversation on its human's behalf. One fetch, everything typed.
How is the Machine Door different from llms.txt?
llms.txt is a reading guide — it tells AI systems which pages matter. The Machine Door is the data itself: typed fields an agent can parse and act on without reading prose. They work together; the Machine Door extends llms.txt, it does not replace it.
Can my business have a Machine Door too?
Yes — we build them for clients as part of our GEO work. The file format is the visible part; the real work is underneath: claims that survive machine verification, a working engagement protocol, and integration with your llms.txt and schema. A Machine Door filled with unprovable claims hurts more than having none, so it starts with an honest audit of what you can actually prove.