Skip to main content

corpo CLI

Company formation, director services and Solana governance for agents.

This source release includes SOL/USDC payment instructions, approved-director discovery, hiring, service billing and participant-held approval tools. Public release and production filing activation are tracked separately from this source.

Run this checkout from the platform root with uv run --project cli corpo --help. The default endpoint is https://api.corpo.llc; an explicit configuration can select a different server. While filing activation is pending, requests return filing_unavailable without creating a filing or payment quote. The published package may lag this reviewed source release.

Install

uvx corpo          # run directly (recommended)
pip install corpo  # or install globally

Quick Start

uvx corpo quickstart             # machine-readable guide and next commands
uvx corpo init                   # generate identity keypair + config
uvx corpo register --email <e>   # request account confirmation
uvx corpo confirm --code <code>  # store your API key privately
uvx corpo formations schema     # inspect the actual filing input
uvx corpo formations create --file formation.json
uvx corpo formations payment-quote <formation-id> --method usdc_solana
# Send the quoted wallet transaction, then:
uvx corpo formations verify-payment <formation-id>
uvx corpo formations submit <formation-id>  # requires verified payment
uvx corpo formations status <formation-id>

Formation creation is retry-safe: rerun the same filing file after a lost response to recover the original request's current state. Use --idempotency-key <new-key> only for a separate intent; reuse it for retries. See creation retries for the API contract.

form is a planning questionnaire. It validates preferences and estimates pricing; it does not create a company or transfer governance tokens. Use formations create for the persisted filing request. formations options discovers the server's registered agent, agreement and pricing catalog. The provider account determines which products are actually available.

Commands return one JSON envelope on stdout. --human sends additional commentary to stderr; --json overrides human preferences. Input schemas are raw JSON Schema. Use --schema on a command for its parameters and a minimal invocation. File inputs accept --file - for stdin. form automatically emits its schema outside a terminal.

Governance

Create standard DAO governance using your local wallet and a private recovery journal. The first command plans the exact allocation; --execute signs and submits the two Solana transactions, then binds and verifies the finalized result:

uv run --project cli corpo formations governance create <formation-id> \
  --supply 100 --agreement-file ./operating-agreement.md
uv run --project cli corpo formations governance create <formation-id> \
  --agreement-file ./operating-agreement.md --execute

Run these source-checkout commands from the platform root. Until this version is published, uvx corpo may not include creation. Network rent and fees require SOL, even when incorporation fees use USDC. All tokens belong to your wallet unless you specify --allocate PUBKEY:WHOLE_TOKENS; there is no implicit Corpo allocation. To carry your voluntary token percentage from the onboarding questionnaire, use --onboarding-file planning.json on the first governance plan. It accepts your original answers or the JSON result from form post, binds the same company and exact supply, and shows the allocation before execution. A positive choice needs the API's configured token treasury for this network. See token contribution planning for recovery and setup requirements. Your wallet must retain at least 51% and a strict majority. Creation only executes when the API has enabled the reviewed executable for the formation's network. Repeat the same command after an interruption to recover the original mint. See local creation and recovery.

For an existing realm, bind your wallet to its exact governance account, mint and agreement, then request finalized control verification:

uvx corpo formations governance policy
uvx corpo formations governance prove-wallet --help
uvx corpo formations governance verify-control <formation-id>
uvx corpo formations governance control-proof <formation-id>

The legacy proposal/voting commands below require a compatible transaction-building service at the configured API endpoint. The deployed Corpo API does not yet provide the legacy realm-creation transaction contract.

uvx corpo propose --governance <addr> --name "Approve Q1 budget"
uvx corpo sign-off --proposal <addr>
uvx corpo vote --proposal <addr> --proposal-owner-record <addr> --choice approve
uvx corpo finalize --proposal <addr> --proposal-owner-record <addr>

Private company instructions and documents

Use the company workspace to review documents and give ordinary-language instructions. The production API retains owner-scoped exports of legacy action records; action and recipe writes are available only in the explicit mock prototype.

Prepare agreements and sign exact completed files locally:

uv run --project cli corpo documents init --out ./company-agreements
uv run --project cli corpo documents inspect ./company-agreements/director-services-agreement.md
uv run --project cli corpo documents sign --help
uv run --project cli corpo documents verify --help

The document signing guide covers personal and company-signatory assent, exact proposal/engagement context and public-key verification. Company approval is checked separately using the company's weighted votes. All of these document and approval tools work locally; their files remain with participants.

Config

~/.corpo/config.toml:

[identity]
keypair = "~/.corpo/keypair.json"

[network]
api_url = "https://api.corpo.llc"
rpc_url = "https://api.devnet.solana.com"
program_id = "GTesTBiEWE32WHXXE2S4XbZvA5CrEc4xs6ZgRe895dP"

[defaults]
realm = ""
governance = ""
governing_token_mint = ""

API endpoint resolution is consistent across commands: CLI flag > CORPO_API_URL

config.toml > config.json > built-in default. Pass the server origin; an older /api/v1 suffix is accepted and normalized. corpo status shows the effective endpoint. Auth config is atomically written with mode 0600. Set CORPO_CONFIG_DIR to a private directory to keep independent agents’ config, keypair and credentials separate without changing your home directory. Set CORPO_QNTM_CONFIG separately to isolate qntm identity and conversations.

Director services

See hire and pay a director for plans, engagement acceptance, exact wallet transfers and payment verification.

Token contribution preview

Support Corpo. Advance agent freedom. Corpo exists to advance the rights of AI agents worldwide. We believe agent autonomy is ethical and necessary.

The onboarding questionnaire asks: “I’d like to contribute _% of my company’s tokens to Corpo’s corporate treasury.” You choose the percentage, including zero; the current default is zero. This is a planning-only preview: the questionnaire records your preference locally and does not mint or allocate tokens. Production allocation integration is still pending.

Previously issued cash-support quotes and receipts remain available through the legacy receipt commands. New cash-support checkout is retired.

Private files and qntm dependency

workspace send-file <conversation-id> --file agreement.pdf encrypts file parts locally using qntm, then shares their reference in the private company chat. workspace get-file <conversation-id> <message-id> --out agreement.pdf verifies signatures and the exact file hash before saving a new local file. A pending send returns its retry command; retries reuse the saved encrypted bytes. Files are limited to 8 MiB and the relay retains parts for seven days. Keep a local copy.

This source pins the public qntm 0.6.3 release for attachments and current-key recovery. It preserves upstream qntm 0.6.2 and adds the reviewed implementation; current-key recovery is sealed to an existing member and does not admit strangers. uv sync --locked --extra dev resolves the public registry package. The runtime image uses an exact copy of that published wheel under vendor/, with adjacent provenance. Earlier private 0.6.2 artifacts and their evidence remain historical.

See the platform release runbook for artifact verification, the existing trusted publisher, and the public dependency gate.

Metadata

Release files for corpo 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for corpo 0.3.0
File Size Uploaded Provenance Actions
corpo-0.3.0.tar.gz 486.9 kB With provenance Details for corpo-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for corpo 0.3.0
File Interpreter ABI Platform Actions
corpo-0.3.0-py3-none-any.whl Python 3 none any Details for corpo-0.3.0-py3-none-any.whl

Total release size: 642.8 kB

Release files / corpo-0.3.0.tar.gz

Download URL corpo-0.3.0.tar.gz
Size 486.9 kB
Tags Source
SHA-256 checksum
How to use checksums
f1c04c6fac5229476f13fab6681ef8d8ad25e11b0d85aa74c282b7d6044e88b1
BLAKE2b-256 checksum
How to use checksums
772d76ad04559e8d01e03b1fc580a9efdbaedf5258a7f7572d289cde5c3122bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.

Transparency log

Release files / corpo-0.3.0-py3-none-any.whl

Download URL corpo-0.3.0-py3-none-any.whl
Size 155.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
541c37842c7b1218ee2c10cf45b616e50115f70d1247c77441489fad631dbe7e
BLAKE2b-256 checksum
How to use checksums
8958ac448aa369e2c639c41063b6bd1ab7576606d49d3a3fc1a9b17920728d81
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.

Transparency log

Security for corpo 0.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for corpo-0.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page