v1 · design partnersoc · console
managed agent + pledge
§ customers

First cohort forming.

OrangeCheck Console is in design-partner mode. The page below is shaped to receive case studies as they ship — three slots reserved for the v1.1 cohort, additional slots open for the v1.2 + v2 windows.

[01]reserved

— · partner 1

AI agent platform

Compliance review unblock target. Audit posture is the deal-breaker for their enterprise pipeline; Console removes it.

agents in review
enterprise pipeline value
integration
mcp · v0.1
[02]reserved

— · partner 2

AI agent platform

Bonded reputation premium-tier candidate. Wants their agents to ship with publicly verifiable delivery histories so customers pay premium for proven agents.

agents in review
pledge bond pilot
integration
tbd
[03]reserved

— · partner 3

mid-market enterprise

Internal agent rollout · compliance can replay every action against the active delegation across an arbitrary window of Bitcoin blocks.

agents in production
audit cycle window
integration
tbd
§ what design partners get

Heavy involvement. Locked-in pricing. The pen on the spec.

  • Pairing. An OrangeCheck engineer pairs with your team for a half-day to wire the integration — MCP, custom adapter, or the bespoke shape your stack needs.
  • Locked-in pricing. v1 launch pricing through the next two annual cycles, regardless of what the public ratecard does at GA.
  • Design influence. Adapter prioritization, scope-grammar idioms, audit-bundle export shapes, federation flows — we co-design with the cohort. The protocol PRs cite design-partner requirements explicitly.
  • Case-study slot. Three reserved on this page; design partners exit via a public outcome on /customers and (where consented) a logo on / .

Apply.

We're selective about the cohort because design influence is real. If your team is shipping AI agents into a regulated rollout, your compliance language is the bottleneck, and OAuth / service-account audit is structurally not enough — you're who we're looking for.