Launch AI Agents and receive structured execution results.
TENZARCH DOCUMENTATION
Build, launch, and observe AI execution on Tenzarch.
Tenzarch connects AI workload demand with distributed execution infrastructure through durable Execution Jobs, Workflow Runs, routing, node assignment, telemetry, usage accounting, and result delivery.
Canonical routesServer-side SDKWallet sessionsNode Rewards boundaries
Start from the product surface, then follow the execution record.
These docs are organized around the real Tenzarch flow: users launch AI Agents, developers submit AI Executions, the backend creates Execution Jobs and Workflow Runs, nodes execute eligible workloads, and the platform returns observable results.
Recommended first read
Start with Tenzarch
Understand the execution network, wallet participation, AI Agents, AI Executions, Free Node activation, and developer access in one launch-ready path.
Open guideArchitectureExecution Network
See how workload demand becomes durable Execution Jobs, Workflow Runs, routing decisions, node assignment, telemetry, and returned results.
Open guideDeveloper integrationTenzarch SDK
Use the published server-side SDK for execution discovery, idempotent submission, job polling, logs, telemetry, usage, and structured errors.
Open guideReferenceAPI Reference
Review the current HTTP routes, authentication requirements, scopes, and backend contract names without changing production routes.
Open guideThe visible product is an entry point into a larger execution network.
AI Agents and AI Executions create workload demand. Behind them, Tenzarch maintains request intake, execution identity, workflow orchestration, lifecycle state, routing, node assignment, distributed processing, operational visibility, result delivery, usage accounting, developer access, and infrastructure participation.
01AI Agents
02AI Executions
03Execution Jobs
04Workflow Runs
05Routing
06Execution Nodes
07Telemetry
08Results
A focused set of launch-critical pages.
AI Agents
User-facing workload experiences that launch trackable execution requests through Tenzarch.
Open documentation →AI Executions
Reusable developer-facing execution capabilities submitted through the Execution Services route surface.
Open documentation →Free Execution Node
Wallet-associated infrastructure participation, activation behavior, availability, eligibility, and Node Rewards boundaries.
Open documentation →Node Rewards
Node Points rules for activation, daily participation, and completed executions without token or earnings claims.
Open documentation →Authentication & API Keys
Wallet sessions, scoped developer API Keys, one-time raw key visibility, rotation, revocation, and server-side usage guidance.
Open documentation →Submit & Track Executions
The production integration pattern from service discovery through idempotent submission, lifecycle tracking, logs, and telemetry.
Open documentation →Wallet Identity
How wallet signatures create authenticated sessions without exposing private keys or recovery phrases.
Open documentation →Logs & Telemetry
How execution state, logs, telemetry, result summaries, and failure reasons should be inspected in production.
Open documentation →Production Integration
A concise checklist for server-side SDK usage, API-key security, idempotency, polling, credits, and failure handling.
Open documentation →Network Operating Model
How Tenzarch separates workload demand, execution records, workflow orchestration, routing, infrastructure, credits, and observability.
Open documentation →One network narrative across users, developers, and infrastructure.
Use scoped API Keys and the SDK from server-side environments.
Execution Nodes provide eligible capacity for routed workloads.