In Scope for Kiln
- Agent-first orchestration and control
- Local device operation + safety guardrails
- Provider integrations for routing/fulfillment
- Unified CLI, MCP, and API workflows
How Kiln Fits in the Stack
Kiln is orchestration and agent infrastructure. It integrates with third-party providers and external provider/network adapters; it does not operate a first-party decentralized manufacturing marketplace/network.
We clarified wording to remove ambiguity and align with existing intent; no strategy change.
Direct Comparison
| Dimension | Kiln | Provider Networks |
|---|---|---|
| Primary role | Agent orchestration/control plane | Supply-side marketplace/network operator |
| Supply onboarding | No direct operator onboarding marketplace | Core function |
| Merchant of record | Provider (for routed jobs) | Provider/network operator |
| Provider visibility | Provider name + terms + provider order IDs preserved | Native provider/network experience |
| Monetization | Orchestration fee on routed jobs | Marketplace/network economics |
Out of Scope for Kiln
- Operating a first-party decentralized marketplace/network
- Owning direct supplier payout rails
- Replacing provider brands as merchant of record
- Provider replacement strategy
API Naming Transition
Canonical provider tools are connect_provider_account, sync_provider_capacity,
list_provider_capacity, find_provider_capacity,
submit_provider_job, and provider_job_status.
Legacy network_* aliases remain for compatibility only.
Deprecated in v0.2.0, removal target v0.4.0.