Open-source. Sovereign by design.

Connect your infrastructure to the new AI network — sovereign, no middlemen.

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.

Download the open-source core Neutral hosting options

Your data. Your node. No algorithm plays favorites.

You own the data

Answers come only from your own portfolio — every supplier you signed. No scraping, no external sources, no surprises.

We stay neutral

Archstone carries capabilities faithfully to the AI. It never ranks offers or decides outcomes — the assistant does, for the traveler.

The principle

Your business capabilities are the source of truth. Everything else is generated.

— why Archstone compiles, instead of asking you to write integrations

Why it hasn't happened yet

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.

Declare once, reach all

One capability contract exposes you to every model at once. The next assistant that matters is a config line, not a project.

How it works

One capability. Every model. Written once.

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.

STEP 01

Describe

State the capability — its inputs, its result, who may call it. Business meaning, not endpoint plumbing.

STEP 02

Compile

Archstone generates the connectors, policy and context layer. Nobody hand-writes integration code.

STEP 03

Every AI invokes

The same capability is discoverable and callable across models — new assistants added without touching your systems.

tourism.search — one declaration

# 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]

Neutral hosting

Don't want to run your own node? We'll host the bridge.

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.

In practice — travel, first

A vacation, bought in a conversation.

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.

Traveler

City break to Rome, October, 4 days, around €700.

→ invokes tourism.search · operator portfolio

tourism.search → result (mocked for this illustration)

[
  { "hotel": "Residenza Trastevere", "area": "Trastevere",
    "eur": 690, "note": "liveliest at night" },
  { "hotel": "Borgo Vaticano", "area": "near Vatican",
    "eur": 705, "note": "quietest, steps from the museums" },
  { "hotel": "Termini Suites", "area": "15 min metro from center",
    "eur": 650, "note": "best value" }
]

The assistant

Three fit your budget. The Trastevere hotel is the liveliest at night; the one near the Vatican is quietest and closest to the museums; the third is €40 less but a 15-min metro from the center. Which matters more — nightlife or quiet?

Traveler

Too expensive.

The assistant

Leave on a Tuesday instead of Saturday and it's €520 — you save €180. Same hotel, same four nights.

Live, not illustrated

Try it in under a minute — any device, nothing to install.

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.

Open Claude — claude.ai, the Claude Desktop app, or the mobile app.
Go to Settings (or Customize) → Connectors.
Click Add custom connector, paste the URL below, click Add:

Connector URL — paste this

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).

Prefer a terminal? Claude Code — one line, same on Mac/Windows/Linux

claude mcp add --transport http archstone-tourism https://demo.archstone.dev/mcp

For transparency: this demo's backend returns fixed, deterministic data — not a live operator's real inventory — so you can see the exact typed shape a capability returns. Same query, same result, every time. Curl it yourself:

Raw capability response — try it

curl -s -X POST https://demo.archstone.dev/v1/search \
  -H "content-type: application/json" \
  -d '{"destination":"Rome"}'

What it returns

{
  "stays": [
    { "id": "stay-5-0", "name": "Riverside Lodge — Rome", "location": "Rome",
      "pricePerNight": 225, "rating": 4.1 },
    { "id": "stay-2-1", "name": "The Olive Court — Rome", "location": "Rome",
      "pricePerNight": 278, "rating": 4.5 },
    { "id": "stay-9-2", "name": "Harbor House — Rome", "location": "Rome",
      "pricePerNight": 331, "rating": 4.9 }
  ]
}