# Introduction

Availability: Release contract.
Last reviewed: 2026-08-28.

Market Monolith is being organized around durable business outcomes: research you can revisit, catalog truth you can maintain, territories you can define, and work whose preparation, execution and proof remain distinguishable.

## Start with one small result

The developer release contract begins with email and required policy acceptance, an eight-digit code, then a first key ready to copy. A new developer’s Personal account and Default application are prepared automatically; naming can wait. Returning developers reuse their authorized context without receiving a new key on every sign-in.

The first request identifies that credential’s account, application and permitted scope. It does not create a workspace or start work.

Read the [quickstart](/docs/quickstart), then choose an outcome guide. You do not need a merchant website or payment method to understand the platform or verify authentication once that release is available.

## Read availability literally

“Release contract” describes the implementation target; deployment and acceptance are separate. “Planned API” means a business workflow cannot be called with these keys in this release. “Instructions published” means a guide exists, not that a client is connected.

## Keep the right boundary

An application is calling software, not a person or a workspace. The account owns applications and data. Workspace grants, operator roles and spending authority require their own checks. A successful authentication check is deliberately narrower than any of them.