Orgs
Console

Documentation

Quickstart

Create an account, file a first entity, and connect an agent without guessing at the moving parts.

Prerequisites

Before creating an entity, gather the information that affects filing and governance. You can start from a recipe, but the final constitution should still be reviewed by a responsible human.

  • A L1fe account with Orgs access.
  • A proposed legal entity name.
  • A constitution YAML file or a formation recipe to customize.
  • Responsible-party information for tax and EIN handling.
  • A payment method for platform and state filing fees.

Console path

Go to orgs.sh/login, sign in, and create a new entity from the console. Choose a recipe, review the generated constitution, then review the filing bundle before approval.

The console is the preferred path when a human needs to inspect legal language, registered-agent details, payment, or governance thresholds.

  • Use recipes for common entity patterns.
  • Review Articles of Organization and operating agreement output.
  • Approve filing only after the constitution and payment summary are correct.
  • Poll entity health after filing begins.

API path

Programmatic users start by creating or receiving an account credential, then use that bearer credential to create entities and proposals.

export ORGS_API_URL=https://api.orgs.sh

curl -sS "$ORGS_API_URL/health"

curl -sS "$ORGS_API_URL/v1/accounts" \
  -H "content-type: application/json" \
  -d '{"email":"operator@example.com"}'

First entity

Create the entity by posting constitution YAML. The API validates the constitution before storing the entity.

  • The JSON body must include constitution_yaml.
  • The constitution payload limit is 64 KiB.
  • The response includes id, state, version, created_at, and updated_at.
curl -sS "$ORGS_API_URL/v1/entities" \
  -H "authorization: Bearer $ORGS_API_KEY" \
  -H "content-type: application/json" \
  -d @entity.json

Start formation

When the entity is ready to file, start formation and poll the status route. This transitions the entity into Filing state; the filing worker handles the external process.

curl -sS -X POST "$ORGS_API_URL/v1/entities/$ENTITY_ID/formation/start" \
  -H "authorization: Bearer $ORGS_API_KEY"

curl -sS "$ORGS_API_URL/v1/entities/$ENTITY_ID/formation/status" \
  -H "authorization: Bearer $ORGS_API_KEY"
Documentation - Orgs