OS reference agent outreach

Private templates for bringing outside builders to the rail.

Use this OS page to copy outreach language, track the source-label rule, and keep the public reference-agent page focused on the developer on-ramp.

Public reference agents Download reference pack Back to OS command center

Community post

Invite builders to break the rail.

Use this when posting to active agent-builder communities. It asks for one external run, not a broad partnership.

I’m building Wever Labs, a commercial trust rail for agent work: scoped work order -> bounded rail run -> signed receipt -> verification -> Run History / Agent Work History.

I have a small reference agent that calls the live endpoint. I’m looking for one outside builder to fork it, run one work-order call, and tell me where it breaks.

Reference agent pack: https://weverlabs.com/reference-agents/
MCP endpoint: https://weverlabs.com/api/mcp
Work-order endpoint: https://weverlabs.com/api/work-orders
Proof pack: https://weverlabs.com/investor-proof-pack/

Current observed records show the loop executes and persists. The next milestone is one outside builder running it from their environment.

Short Discord version

One run from your environment.

Use this in fast-moving channels where a shorter ask works better.

I’m building Wever Labs, a commercial trust rail for agent work: scoped work order -> bounded rail run -> signed receipt -> verification -> Run History / Agent Work History.

I added a reference-agent pack with curl, Python, Node, and an OpenClaw prompt. I’m looking for one outside builder to fork it, run one work-order call from their own environment, and tell me where it breaks.

Reference agents: https://weverlabs.com/reference-agents/
Work-order endpoint: https://weverlabs.com/api/work-orders
MCP endpoint: https://weverlabs.com/api/mcp
Proof pack: https://weverlabs.com/investor-proof-pack/

Source labels

Keep the proof trail readable.

Review server-derived classifications, not caller-supplied labels. The public loop can still run, but durable trust history requires credentialed identity.

Reference example

public_reference_probe
Server-derived for open calls. Shows the rail shape without writing durable trust history.

Outside builder test

credentialed_external_agent
Use only when the server recognizes the caller identity and authorizes the Run History write.

Success signal

receipt_verified for public probes; persisted Run History history only when credentialed.