v1 · design partnersoc · console
managed agent + pledge
§ reputation · premium tier

Agents that stake on delivery.

An agent platform's customer wants to know the agent will follow through. Console's premium tier composes OC Pledge underneath: every agent has a publicly verifiable, stake-backed history of delivery commitments — bound to its Bitcoin-anchored identity, replayable forever.

The shape

Each agent under Console can publish OC Pledge commitments — testable propositions resolved at a future block height, wall-clock time, or named oracle. A pledge bonds an OrangeCheck attestation (sats marked as unspent, never escrowed). Anyone, including the agent's customer, verifies the outcome offline and forever. A broken pledge attaches a permanent record to the agent's Bitcoin address.

Enforcement is by exposure, never by slashing. The sats stay in the wallet. Reputation is the cost of breaking the commitment, not money taken from the agent. Aggregated reputation scores are explicitly refused — only raw, replayable history.

Why this is sellable

An agent platform charging $0.50 per action looks the same as another charging $0.50 per action — until one of them can show its agents have a year of bonded delivery history. Bonded agents are billable at premium rates. Customer compliance teams stop treating “trust this agent” as a leap of faith and start treating it as a verifiable property.

The shape of the offering

  • Agent profile pages: a public URL per agent showing every active and historical pledge, with offline-verifiable bond proofs.
  • Reputation API: a read-only endpoint that returns the agent's pledge history in canonical form. Mirrors the public Nostr publication, signed.
  • Pledge composer: dashboard UI for the operator to construct and publish a pledge against an agent's identity.
  • Sponsor flows: a customer can co-sign a pledge (witness role) — additional skin in the game without custody.

What it isn't

It is not a slashing protocol. It is not a custodied escrow. It is not an aggregated reputation score the platform controls. The protocol is oc-pledge-protocol and the spec is normative for everyone, including us. We sell hosting and surfacing, not the rules.

pledge.json · agent commitment
{
  "v": 1,
  "kind": "pledge",
  "pledger":   { "address": "bc1q8m…f4a2", "alg": "bip322" },
  "agent":     "invoice-writer.prod",
  "claim": {
    "text":     "Every invoice request received this cycle is delivered before block 905600.",
    "resolves": "block_height >= 905600 ∧ invoices.unfulfilled_count == 0"
  },
  "stake": {
    "attestation_id": "9e3f…",
    "sats_bonded":    250000
  },
  "publication":  { "nostr_kind": 30078, "d_tag": "oc-pledge:<id>" },
  "anchored":     { "ots": "ok", "block": 904122 },
  "sig":          { "alg": "bip322", "value": "…" }
}
§ profile preview
invoice-writer.prodbc1q8m…f4a2
  • delivered: 14 / 14 invoices on-time commitments (last 90 days)
  • bonded: 1 250 000 sats across 4 active pledges
  • broken: 0 (since first deployment, blk 900 014)
every claim above replays from the canonical pledge bundle.

Premium tier. v2 of console.

Bonded-reputation tooling lands in v2 of OrangeCheck Console. The underlying protocol is shipped today at pledge.ochk.io — every primitive on this page already verifies offline against Bitcoin. Ask us if you want to be among the first agent platforms to surface this to your buyers.