Connections

Every interface commits to your corp repo. Whether a human types a command, an agent runs autonomously, or a CI pipeline hits the API — the result is a git commit with the same provenance, the same policy gate, and the same audit trail.

CLI

The corp CLI is the primary human interface. Terminal-first, scriptable, composable. Every command produces a git commit.

$ corp form \
    --name "Acme Inc" \
    --type corporation \
    --jurisdiction US-DE
  ✔ Formation submitted

$ corp cap-table issue-equity \
    --entity-id ENT_ID \
    --grant-type common \
    --shares 4000000 \
    --recipient "Alice"
  ✔ Equity grant issued

$ corp status          # Entity overview
$ corp obligations     # Pending actions
$ git log --oneline    # Full history

REST API

Full REST API with auto-generated OpenAPI documentation. Every mutation is a git commit. The response includes the commit SHA.

$ curl -X POST \
  http://localhost:8001/v1/formations \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Acme","state":"DE"}'
  ✔ intent_id: 9df8...  receipt_id: 2be1...

AI Agents

Agents commit to your repo autonomously. They observe corporate state, generate candidate intents, pass them through the policy gate, and commit the results. Each agent runs in a sandboxed container with scoped authority and budget controls.

  Agent: compliance-bot
  ────────────────────
  [f1a2b3c] check compliance deadlines
  [a2b3c4d] prepare DE annual report
  [b3c4d5e] file franchise tax ($400)

  Agent API:
    POST /v1/agents
    POST /v1/agents/{id}/messages
    GET  /v1/agents/{id}/executions
    GET  /v1/agents/{id}/logs

BYO API key — Anthropic, OpenAI, or OpenRouter. No platform fee, no markup.

MCP Server

36 MCP tools over JSON-RPC. Every tool call that mutates state produces a git commit. Connect any MCP-compatible client — Claude, GPT, or your own agent.

  MCP Tools (36 total):
    form_entity        → commit
    issue_equity       → commit
    check_compliance   → read
    generate_document  → commit
    file_report        → commit
    create_safe        → commit
    get_entity_status  → read

Git Integration

Your corporation is a git repo. Standard git workflows apply.

$ git clone https://thecorporation.ai/acme.git
$ git log --oneline
$ git push origin main
$ git remote add github \
    [email protected]:you/corp.git

• GitHub / GitLab compatible — mirror your repo anywhere
• Webhooks — trigger CI/CD on corporate events
• Pre-commit hooks — custom validations
• Branch protection — require reviews for sensitive actions

Event Bus

Corporate events are git commits. Subscribe to them in real time.

• Webhooks — HTTP POST on any commit
• Digest emails — daily summary of activity
• Audit log — git log is the immutable audit trail

Bank Connectors

Ingest bank feeds from supported providers. Transaction data is committed to your repo for categorization, reconciliation, and reporting.

• Mercury
• Silicon Valley Bank
• First Republic
• Generic CSV / OFX import

TypeScript SDK

Build custom agents and integrations. Every mutation returns the commit SHA. The SDK wraps the API — same pipeline, same guarantees.

$ npm install @thecorporation/corp-tools

import { CorpAPIClient }
  from "@thecorporation/corp-tools";

const client = new CorpAPIClient(
  "http://localhost:8001",
  process.env.CORP_API_KEY,
  process.env.CORP_WORKSPACE_ID
);

const formation = await
  client.createFormation({
    name: "Acme Inc",
    state: "DE"
  });