oc·docs
live · mainnetoc · docs
specs · api · guides
docs / overview

OC Fleet

Managed infrastructure for the OC Agent family. fleet.ochk.io is where customers register their BIP-322-signed delegations, ingest stamped agent-action envelopes from their LLM tool calls, anchor every receipt to Bitcoin via the OC Stamp pipeline, fan out signed deliveries to subscribed webhook endpoints, and export verifiable audit bundles for compliance — without running their own Postgres, Nostr publisher, or OTS calendar relay.

The protocol surface is the same OC Agent + OC Stamp + OC Pledge primitives documented elsewhere in these docs. Fleet is a commercial layer on top: same envelopes, same canonical messages, same offline verification — packaged as a SaaS so a typical customer ships in an afternoon instead of a quarter.

What fleet is, and what it isn't

IsA turnkey operator dashboard for OC Agent envelopes. Sign in with your Bitcoin address, register delegations, watch action receipts stream in, audit-export at any time.
IsA managed publisher. We sign Nostr events for you (kind 30083 / 30084 / 30085 / 30086), submit OTS commitments to the calendar set, and re-publish on relay flake.
IsA webhook delivery layer. Subscribe an HTTPS endpoint; we POST HMAC-signed events on every accepted envelope, retry with exponential backoff, surface delivery health.
IsA billing surface. Lightning rail (BTCPay) is primary; Stripe is the USD parity rail. No token, no custody.
Isn'tA new protocol. Every envelope fleet persists is identical to one a customer could publish themselves directly via @orangecheck/agent-cli.
Isn'tA signer. Fleet never holds principal keys. Every delegation is BIP-322-signed in the customer's wallet (UniSat, Xverse, Leather, OKX, Phantom, or paste-in).
Isn'tA trust anchor. Verifiers don't trust fleet — they trust the signatures on the envelopes fleet publishes. Drop the bundle into @orangecheck/agent-core and verify offline.

Where to go next

  • Quickstart — sign in, bootstrap your project, register your first delegation in five minutes.
  • Integrations — drop-in adapters for Anthropic Tool Use, OpenAI function calling, Vercel AI SDK, LangGraph, and MCP. Three lines of config and your tool calls flow into fleet.
  • API reference — OpenAPI 3.1 spec, Bearer-auth examples, error codes.
  • Webhooks — receive signed POSTs on every event your endpoint subscribes to.
  • Audit export — pull the bundle (NDJSON / JSON / CSV) and verify offline.

Five-second mental model

your LLM tool call
   │
   ▼
@orangecheck/agent-anthropic (or openai / vercel / langgraph / mcp)
   │  stamp the call → ActionEnvelope (BIP-322 signed by the agent)
   ▼
fleet.ochk.io /api/actions
   │
   ├─→ Postgres                 # your tenant-scoped registry
   ├─→ Nostr kind 30084         # public, censorship-resistant transport
   ├─→ OC Stamp pipeline        # batched into Bitcoin block via OTS
   └─→ webhooks                 # signed POST to your subscribers

Every receipt is content-addressed (sha256(canonical_message)), BIP-322-signed by the agent's address (which the parent delegation bound), and verifies offline forever — even if fleet disappears tomorrow.