BUILD THE SERVICE.

Developers can build applications and services on top of OX without first building another permanent proprietary version of every human. Connect to consenting Machine Selves™. Build applications. Build integrations. Build companies. The human relationship remains with the human.

BUILD THE SERVICE. DO NOT OWN THE HUMAN.

Where verified and authorised, developer documentation can explain Quest routing, decentralized matching, permission architecture, disclosure rules, identity / credential proofs, application interaction, provider portability and value interactions.

DEVELOPER ACCESS

APIs, SDKs, documentation, tools, protocol access, technical access, applications, integrations and permission requirements belong in the developer path.

TOOLS

Tools belong in the developer path where available and authorised.

PROTOCOL ACCESS

Protocol access belongs in the developer path where available and authorised.

TECHNICAL ACCESS

Technical access belongs in the developer path where available and authorised.

APPLICATIONS

Build applications on top of OX.

INTEGRATIONS

Build integrations without owning the human relationship.

PERMISSION REQUIREMENTS

Connect to consenting Machine Selves™. Permissions remain with the human.

QUEST ROUTING / MATCHING ARCHITECTURE

REQUEST / QUEST
THE REQUEST MOVES.
Relevant Machine Selves™ evaluate MATCH? PERMITTED? ENABLED?
Matching authorised nodes: "I MATCH"
MATCH FIRST. REVEAL ONLY WHAT IS NECESSARY.
Authorised interaction / action

DISCLOSURE RULES / IDENTITY AND CREDENTIAL PROOFS

Where verified and authorised, developer documentation can explain disclosure rules and identity / credential proofs.

PROVIDER PORTABILITY / VALUE INTERACTIONS

Where verified and authorised, developer documentation can explain provider portability and value interactions.