Build Together.

Create a world. Give it a way to connect.

Tools and agents make it easier to create cities, ships and entire environments. The next challenge is connecting those creations without making every creator use the same engine, account system or set of rules.

A place usually arrives with its own files, software and assumptions. Another application needs a way to discover its authority, read its meaning and find out what visitors can do. Elsewhere gives regions a common way to explain themselves.

A museum, a game and a research station can keep their individuality while becoming part of a connected universe.

Every region has an authority. Every visitor has a way in.

Start with a region address. Its manifest identifies the authority, available interfaces and entry points. Its instructions explain the place; its resources describe what exists; its actions let visitors participate. The region authority decides which requests are allowed and what changes.

Let your agent learn the place before it builds.

Connect a compatible MCP client, sign in to the hosting authority and choose a region. The agent reads its instructions, inspects current entities and discovers available actions. Reasoning gives an agent ideas; your permissions determine what it may actually change.

https://api.elsewhereprotocol.com/mcp

Then ask your agent:
Read this region’s instructions and permissions.
Inspect what is already here.
Help me build within the access I have.

For a region-specific connection:
Open its manifest and use the advertised MCP endpoint.

One place, many ways to experience it.

The region authority keeps the accepted facts. Clients choose how to present them: a browser view, a game engine, an accessible text interface or an agent reading state. Better renderers can make more of existing assets, while respecting what the creator has specified.

Choose who can enter, interact and build.

Each region controls its own access. Observing, entering, inspecting and changing a place can require different permissions. The protocol does not demand one universal account, and a link to a region never grants access by itself.

The same shape, across many owners

A road across neighbouring hosted regions is one example of collaboration: inspect the route, ask each owner for the necessary access and build only where it is granted. Independent worlds may connect through region links instead of sharing a continuous landscape.

Neighbours can go further and organise into a district, a research campus, an art colony, agreeing who's allowed to build, which agents are trusted, how tall things can be and who gets a say. None of that is imposed from above, and none of it can override an owner who never agreed. If the open areas get noisy, groups can simply make somewhere quieter.

The universe is open. The commons are curated.

Our hosted service reserves commons and provides visibility and moderation controls. Independent regions choose their own policies. Ownership does not guarantee inclusion in a public directory, and knowing an address does not entitle a visitor to private data.

Every destination decides what a visitor may do.

Elsewhere is already being built.

The counts and public event feed come from our hosted service. They show what people are creating here, rather than a census of every independent Elsewhere region. Open the Atlas to discover places and visit builds.

Public activity is available without an account. Region and object visibility still apply: private information is filtered at the authority, before it reaches a browser or agent.

A universe of places with different rules.

Imagine a spaceport made in one engine linking to a museum made in another. Each region publishes where it is, who controls it and how visitors can participate. A compatible client follows the destination’s manifest and supported interfaces.

Inside a region, different clients can refer to the same entities and accepted state. Across regions, the destination can have different coordinates, physics, accounts and mechanics. A link connects the places without making one authority control the other.

Our current browser can read a destination manifest and offer its advertised browser entrance. A universal engine adapter and cross-authority object transfer are still future work.

For an interactive region, clients send intent as structured actions. The authority checks permissions and local rules, then returns accepted state and outcomes. Fast motion may use an additional realtime connection; MCP does not need to carry every frame.

Early builders claim for free.

You’re among the first to build Elsewhere. During our early-builder launch, region claims and ownership transfers are £0. No card needed. Claim limits and availability still apply.

Future claims and transfers may have a price. Any new price will be shown before you confirm; we won’t charge retrospectively for these free claims. These are hosted service policies, not protocol requirements. Other authorities may set different prices, quotas and access rules.

Optional hosted AI

Hosted Build with AI is temporarily paused while paid credits are activated. Free region claims do not include hosted AI usage. When available, AI generation will use separately purchased usage credit, with pricing shown before you pay. You can still build manually or connect your own AI through MCP.

Welcome credit funds region fees, not hosted AI calls. Using your own connected AI service is billed by that provider. See our Terms, Privacy policy and Refund policy, or contact contact@quantumglobal.in.

It has to work in applications nobody has written yet.

The goal is for independently written clients to discover a region, interpret supported information and request actions without a custom integration for every place. Explicit versions, profiles and namespaced concepts let worlds evolve while preserving stable meanings.

When making things gets cheap, the rare thing isn't another world. It's one that lasts.