Tracking: IPTO PI as Switchboard Hosted Standard customer (arms-length)

[abhicris]

Problem

IPTO PI (the agentic-use product) needs a payment runtime to meter and settle per-query agent payments. Switchboard Hosted Standard tier maps cleanly to the IPTO PI workload: x402 envelope on the agent side, AgentEscrow lifecycle on the settlement side, no IPTO-specific code in Switchboard.

This is a tracking issue for the integration. IPTO and kcolbchain are independent companies that share a founder — the relationship is arms-length per the canonical scoping doc.

Proposed Approach

1. Provision IPTO PI as a Switchboard Hosted Standard customer. Standard tier pricing applies; no special accommodation. Billing email = IPTO accounts.
2. Wire IPTO PI to call Switchboard endpoints for the x402 paywall on per-query agent payments. No IPTO-side code into switchboard; no switchboard-side code into IPTO.
3. Manifest spec: IPTO CLI indexes Muzix catalog manifests via the standard licence-attribution-provenance schema. Manifest stays OSS at switchboard repo; IPTO consumes it via stable schema URL.
4. Settlement layer: Switchboard settles via CR8-USD (cross-vertical) or MUSD (music) on Create Protocol L1. Invisible to IPTO's data-owner customers.

Acceptance Criteria

• IPTO PI deployed against Switchboard Hosted endpoint, e2e a representative agent query flow
• Standard tier billing record created
• Muzix manifest schema URL stable and documented in docs/manifest-spec.md
• Public framing for any joint post follows the arms-length rules (no "Create Protocol gets IPTO's pipeline" / no "IPTO is on Create Protocol" / common-founder disclosure inline)
• Either side can terminate with 30-day notice; month-to-month only

References

• internal: see IPTO arms-length scoping doc (2026-06-01) and switchboard 2-SKU econ model (Hosted Standard)
• Public switchboard hosted surface — standard tier