> For the complete documentation index, see [llms.txt](https://vordai.gitbook.io/vordai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vordai.gitbook.io/vordai-docs/readme.md). # Vordai Docs ### Vord Vord is a private AI inference platform designed to separate account and funding activity from inference requests. Account identity, payment data, account cookies, and account tokens are not sent with prompts to the inference gateway. ### Available today * OpenAI-compatible streaming chat completions * 30 publicly listed text-model routes * Live model discovery at GET * Live built-in tool discovery at GET * File parsing at POST * Intel TDX node attestation at GET #### Signed model catalog GET is the source of truth for model IDs, context windows, capabilities, privacy metadata, usage limits, and published prices. Availability is dynamic, so integrations should read the live catalog rather than infer capability from a model name. The model catalog is a signed taxonomy-v2 bundle. Clients may verify model\_taxonomy\_version, bundle\_digest, source\_bundle\_digest, publisher\_key\_id, and publisher\_signature. Interpret privacy\_tier, privacy\_capabilities, model\_sets, and traits as separate fields; none should be inferred from another. The uncensored model set applies only to models explicitly listed in model\_sets. The most\_uncensored trait is a recommendation signal and does not establish model-set membership or guarantee unrestricted model behavior. In the current live catalog, every model\_sets array is empty. #### Privacy tiers and capabilities Vord publishes two privacy tiers: anonymized and private. TEE attestation and E2EE are separate signed privacy capabilities. Clients should verify the live route metadata and the documented evidence boundary before making a security claim. The current catalog contains 28 anonymized routes and 2 private routes: tee-glm-5.2 and tee-kimi-k2.6. Both private routes currently declare e2ee and tee\_attestation in privacy\_capabilities. #### Built-in tools Discover the current built-in tool schemas with GET . Use the returned exact function schemas, tool\_catalog\_version, and tool\_catalog\_digest; do not treat a hard-coded documentation list as the long-term source of truth. The current live snapshot reports tool\_catalog\_version account-r71 and tool\_catalog\_digest sha256:2a750b05b534034a7dfd7dc64449a26318867cc4202c1651bd67d83cdcb6bf78. It contains calculator, fetch\_url, current\_time, and web\_search. The model catalog currently declares tool calling on 6 models, web search on 5 models, and both capabilities on 5 models. Web search is metered per actual invocation. Consult metered\_unit\_prices and maximum\_usage in the selected model's live catalog entry. #### File parsing File parsing is available at POST . The current public contract supports PDF, EPUB, DOCX, PPTX, XLSX, and XLS documents with a 25 MiB file limit and an active Vord Session credential. Text and source files are read locally where possible. Original files and extracted text are not persisted in ordinary database, object-storage, log, or backup paths. Parsed content is sent to a model only when the user submits the request. #### Node attestation Node attestation is available at GET . The response provides Intel TDX node evidence bound to the current TLS public key. The bounded conclusion is TDX NODE VERIFIED. It does not verify the workload image, source code, runtime arguments, or operator exclusion. ### Beta / rollout pending #### Credits and device wallet 1 Credit equals 1 cent. Credits are blind-signed, device-held bearer credentials protected by P2PK keys. Anyone with the corresponding proof and private-key material can spend them; exporting that material transfers practical spending control. Credits purchase, encrypted device storage, encrypted backup, recovery material, crypto funding, account balance conversion, and the unified Get credits, Top up, and Backup experience remain subject to rollout gates. #### Sessions and request recovery Session open, close, automatic close, claim, preflight, billing lookup, and recovery are Beta / rollout pending. Direct-mode recovery does not replay or reconstruct response text. A separate opt-in Response Spool path is Beta / rollout pending; when enabled, it resumes the same accepted request from short-lived encrypted frames and never creates a second provider execution. The Response Spool feature gate is not generally open. Other rollout-pending surfaces include browser OAuth for the CLI, account device management, the TypeScript SDK, CLI, shared purchase and recovery core, and web chat with device-local conversation history. ### Coming Soon * Optional device-local App Screen Lock with a 4-digit or 6-digit passcode. It is a screen-privacy control and does not replace the recovery key or add a new Credits-encryption layer. * Video generation APIs and media-capable routes. They remain under integration and are not generally available. * Optional subscriptions and card funding that preserve the account-to-inference separation * Python SDK, additional providers, and more tools * Chat-only PWA support with a read-only offline shell and encrypted-backup export ### Availability policy Available means the capability is exposed by the live service or catalog. Beta / rollout pending means implementation or a public contract exists but general availability has not been confirmed. Coming Soon means an approved product or implementation plan exists, but the capability is not yet available. Candidate ideas and undecided provider or product options are intentionally excluded.