Digital interaction is changing: AI assistants are becoming the new gatekeepers of discovery. Archstone is an open-source protocol that plugs your services directly into any AI model. Describe the capability once, and stay independent of platforms that charge tribute or decide who gets seen.
Your data. Your node. No algorithm plays favorites.
Every AI is its own integration project. Your APIs were built for people, not agents. So the channel that matters most is the one you can't staff for.
A CTO knows the AI channel is coming, but can't spare three developers for months of work per model. Archstone turns that whole effort into a single description — written once, kept in sync for you.
You declare a capability — what your business can do, in plain business terms. Archstone compiles it into the interfaces each AI speaks, and keeps them in sync. Three steps, and the last one repeats for free.
State the capability — its inputs, its result, who may call it. Business meaning, not endpoint plumbing.
Archstone generates the connectors, policy and context layer. Nobody hand-writes integration code.
The same capability is discoverable and callable across models — new assistants added without touching your systems.
# a capability is what you do, not how your API is wired capability: tourism.search description: Find trips matching a traveler's intent. input: destination: location dates: date-range # flexible — prices vary by day travelers: party budget: money # optional output: offers: collection<Offer> # from your portfolio only policies: [authenticated, rate-limited]
Some teams would rather not manage their own server — that's fine. Hosting is optional, and it's pure utility: no bidding wars that rank one business above another. We host the technical bridge; you keep absolute control over where it leads.
Available on request while we build self-serve hosting — write to us and we'll set it up for your capability.
Your business capabilities are the source of truth. Everything else is generated.— why Archstone compiles, instead of asking you to write integrations
Answers come only from your own portfolio — every supplier you signed. No scraping, no external sources, no surprises.
Archstone carries capabilities faithfully to the AI. It never ranks offers or decides outcomes — the assistant does, for the traveler.
One capability contract exposes you to every model at once. The next assistant that matters is a config line, not a project.
Tourism is where Archstone proves itself first. The traveler never touches a booking form. They talk — the AI reads the intent, calls your capability, and explains the trade-offs in words.
Illustrative scenario. Offers, availability and prices resolve live against the operator's own systems.
tourism_search is the same 12-line capability shown in "How it
works" — already compiled, hosted live. This works the same way on Mac, Windows,
the web, or your phone: no config file, no terminal, no sandbox account.
https://demo.archstone.dev/mcp
Then ask about a trip — a destination, a
date range, a budget. Claude calls tourism_search against a real backend
and answers from the typed result: the exact loop above, live. Works on Free, Pro,
Max, Team and Enterprise plans (Free accounts get one custom connector — this is it).
claude mcp add --transport http archstone-tourism https://demo.archstone.dev/mcp
We build the first working version with you, on your data. You shape the product, and you enter the AI channel before your competitors do.
or write to us directly at [email protected]