Skip to content

Tracking: Hanzo hanzoai/agent reference integration (paid SOW) #81

@abhicris

Description

@abhicris

Problem

Hanzo ships agent runtime infra (IAM, durable-workflow, hanzoai/agent tool-call layer). Switchboard ships the programmable-payment substrate (x402 + AgentEscrow + MPC wallet). The integration that maps cleanly is Switchboard as the payment runtime below hanzoai/agent's tool-call layer.

This is a tracking issue for the paid scoping engagement. Deliverable is a public reference deploy with both org logos, plus a joint technical writeup.

Proposed Approach

Milestone breakdown (~4-5 weeks total):

M1 — Integration architecture doc (Week 1-2):

M2 — Reference implementation (Week 2-3):

  • Minimal viable deploy: one real agent flow (code-execution-pay OR inference-pay OR storage-pay — Hanzo's call)
  • Public repo with both org logos
  • E2E test that runs the flow end-to-end

M3 — Joint technical writeup + benchmarks (Week 4):

  • Loom walkthrough
  • Hanzoai blog post + cross-post on switchboard docs
  • Latency / gas / cost numbers

M4 — Handoff + production-readiness checklist (Week 5):

  • 30-min sync on what unblocks a production deployment
  • Notes on hosted-Switchboard-inside-Hanzo-enterprise (if interesting on their side)

Acceptance Criteria

  • M1 doc reviewed and signed off by both Hanzo + kcolbchain technical leads
  • M2 reference deploy passes E2E test in CI
  • M3 writeup published with both org bylines
  • M4 handoff doc + production checklist filed

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions