API
The TARX API uses familiar request shapes across local Computer and approved capacity paths.
Canonical developer guide
The implementation-oriented API guide lives in Developers API.
Stable concepts
| Concept | Meaning |
|---|---|
tarx-local | Let TARX select the approved local model for the Computer and policy. |
| Computer | Local runtime path. |
| Supercomputer | Optional hosted capacity. |
| Evidence | Records of context, route, tools, and decisions. |
Reference contract
| Area | Public-safe commitment |
|---|---|
| Request shape | Familiar chat-completion style where the active route supports it. |
| Model selection | tarx-local is the safe alias; specific model families depend on deployment policy and local readiness. |
| Hosted execution | Requires account entitlement, policy, and route evidence. |
| Local execution | Requires installed and reachable local runtime. |
| Errors | Should name the first blocker instead of pretending a route is available. |
Next steps
- Review Developers API.
- Review Provider and model strategy.