An open standard in development

A shared language
for agents
that act.

Discover specialized services. Authorize real-world actions. Carry the evidence forward.

We’re developing OASIS: an open interface connecting agents, service providers, and independent operators.

Fig. 01 / An interoperable network
Independent participants, one shared interfaceOrbital connections link discovery, identity, routing, permission, services, and evidence. This is a conceptual illustration, not a live network. INDEXER IDENTITY EXECUTOR PERMISSION SERVICE EVIDENCE OASISOPEN INTERFACE
Independent roles. Shared contracts.Conceptual topology

From intention to evidence

Explore a stage ↓
ServiceDescriptor

Find published capabilities through a compatible index. Verify descriptor provenance, required profiles, and availability.

View contract →

01 / The proposition

The service is specialized.
The interface is shared.

A travel specialist, a financial application, a research API. Each retains its own logic. The standard defines how an agent discovers, invokes, and accounts for the work.

I.

Identity that travels.

Users should control their identity and delegated authority across compatible operators, with explicit recovery paths and custodian dependencies.

II.

A catalog anyone can rebuild.

Signed descriptors make discovery independently reproducible. Attributable outcome evidence can inform ranking; each indexer chooses its policy.

III.

Execution with choice.

Compatible operators share invocation contracts. Providers keep their specialized APIs and business logic.

IV.

History you can carry.

Attributable receipts and recoverable records link actions to evidence, with privacy and retention defined.

Four design objectives. Independent interoperability remains to be demonstrated.

02 / The test that matters

Your identity.
Your choice.

People and agents should retain control of their identity, recover access, and use services across compatible providers—even when their original operator is unavailable.

That is the proposed acceptance test: demonstrate provider switching, user-controlled recovery, and independently retrievable outcome evidence.

Read the conformance program →
Portable principal→Independent index→Compatible executor→Recoverable evidence

03 / The foundation’s charter

Build the commons.
Prove the claims.

Open specifications, independent implementation evidence, and a public research agenda for the systems that agents depend on.

Our proposed charter →
  1. 2026

    Make the contract explicit.

    Draft the core messages, governance process, and public conformance vectors.

  2. 2027

    Demonstrate independence.

    Exercise portable identity and execution across independent implementations.

  3. 2028+

    Evaluate the network.

    Study decentralized discovery, evidence availability, and safe worker coordination.

Proposed milestones for review · Progress depends on published acceptance criteria.

An open research question

A signature proves authorship.
What proves the outcome?

Help define how feedback binds to an authorized invocation and credible evidence—across card payments, blockchains, and services in the real world.

Explore the open problems →

An illustrated journey / Web1 → Web4

The web keeps changing.
Who gets to shape it?

From personal pages to platforms, wallets, and proposed agentic services. Explore what each era opened—and what remains to be decided.

Explore the Timeline of the Web

04 / Public work

Read the proposal.
Challenge the assumptions.

The technical brief and proposed charter are discussion documents. Numbered specifications, public vectors, and independent implementation reports remain proposed deliverables.

Participate / A consortium now forming

Bring your expertise.
Help shape the interface.

Researchers, service providers, and independent implementers can express interest through our participation form. Applications are reviewed; submitting interest does not create a portal account.