Docs
Devory is early, and the SDK and CLI are earlier still. This page states what each surface actually does right now, not what it will eventually do. It covers the same components, protocols and interfaces a human developer or an AI agent uses to compose with Devory, documented at whatever depth is real today. Nothing below is a simplified tutorial standing in for a missing feature.
A typed TypeScript client for calling the Devory Gateway. Today it is a thin transport layer that does not yet know about projects, graphs or Marketplace listings by name. A component-authoring workflow is planned, not available yet.
A terminal interface into Devory. Today it parses arguments, prints version information and runs a local health check. Commands for authentication, projects, graphs, qualification and Marketplace publishing are designed but not implemented, and fail loudly rather than pretend to succeed.
The capability, resource-scope, operation, audit-envelope and external-agent-principal contracts an AI agent is built against, and how the MCP transport carries them.
Read the protocol overviewHow a component is structured (type, configuration, inputs, outputs, version, state and connections), and the qualification pipeline it must pass before it can be reused.
Read the component modelA reference for a capability that does not exist yet is not documentation. It is a promise dressed up as one. As the SDK, CLI and protocol surfaces above become real, this page grows with them, in the same honest, dated way as the rest of the site.
