For partners¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Ways to partner¶
| Partner | What you publish or integrate | Where it is designed |
|---|---|---|
| Asset publisher | agents, skills, workflows, tools, model profiles | asset publication, marketplace |
| Template publisher | ConnectSoft-compatible templates and libraries | Template & Library |
| Connector publisher | connectors to your system with conformance evidence | Integration platform |
| MCP server provider | tools, resources and prompts behind the governed executor | Tools & MCP |
| Agent interoperability | your agents discovered and called through A2A agent cards | agent cards |
| Integrator | building and operating products for customers on the Factory | Generated SaaS, fleet operations |
Certification and evidence¶
Nothing is listed without being Published through asset publication with evaluation evidence (quality gates, decision D32), and nothing is public without a certified publisher and a Platform admin approval. Connectors pass conformance runs; MCP servers are registered and authenticated; tools carry side-effect classes. The marketplace distributes, it never publishes (marketplace security).
Commercial terms¶
Listings carry a pricing plan (free, included in an edition, per seat, per usage, one-time) with a publisher revenue share; acquisition bills the customer's Factory subscription; usage pricing meters through the Factory's metering. Partners are certified publishers with an agreement and payout details by reference (licensing).
Technical surface¶
- MCP for tools, resources and prompts (ADR-0022); A2A for agent discovery and task interoperability (ADR-0023); OpenAPI and gRPC through the public Control plane API (GW-03) with workload identity.
- Blueprints and descriptors have JSON Schemas (schema registry); templates are discovered from repositories with pinned manifests.
- Everything a partner's asset does inside a customer's tenant runs under that tenant's policy, classes and approvals; receipts are the customer's.