TensorifyDocs

API Reference

This page is intentionally conservative.

Current public docs stance

The public site should not pretend there is a polished, fully documented managed execution API for the current MVP.

What matters publicly right now is:

  • the app workflow editor
  • the local CLI loop
  • selected-node testing and debugging

What this page can say honestly

Tensorify has internal application and workflow APIs that support the editor and the local watch-and-test loop, but the public marketing/docs site should avoid inventing a stable external API surface that users can rely on today without verification.

If you are evaluating Tensorify today

The safer path is:

  1. use the app for workflow editing
  2. use the CLI for local execution
  3. use the current docs around quick start, installation, and core concepts

What is deferred from public API positioning

This page should not currently promise:

  • managed cloud execution endpoints
  • polished public execution status APIs
  • public rate-limit and plan matrices
  • finished SDK availability stories

Next