> 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/guides.md). # Guides ### Choose a model safely 1. Read GET . 2. Select an exact live model ID. 3. Check capabilities, context and output limits, prices, and maximum\_usage. 4. Interpret privacy\_tier, privacy\_capabilities, model\_sets, and traits as independent fields. 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. The current live catalog publishes empty model\_sets arrays. ### Choose a privacy tier Vord publishes two privacy tiers: anonymized and private. TEE attestation and E2EE are separate signed privacy capabilities, not additional tiers. The current live catalog contains 28 anonymized routes and two private routes: tee-glm-5.2 and tee-kimi-k2.6. Both private routes currently declare e2ee and tee\_attestation. Do not infer privacy from a model name or prefix. Verify live route metadata and the documented evidence boundary before making a security claim. ### Verify the signed catalog 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. Use these integrity fields to detect stale or altered catalog data. Do not infer one taxonomy field from another. ### Use 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 contains calculator, fetch\_url, current\_time, and web\_search. Only send tools when the selected model's capabilities array declares tools. Only enable web search when the model declares websearch. Web search is metered per actual invocation. Read metered\_unit\_prices and maximum\_usage from the selected model entry. ### Parse a document File parsing is available at POST . The current public contract supports: * PDF * EPUB * DOCX * PPTX * XLSX * XLS Requests require an active Vord Session and have a 25 MiB file limit. 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. ### Verify node attestation Node attestation is available at GET . 1. Generate a fresh 32-byte base64url nonce. 2. Request the attestation response. 3. Verify the nonce and TLS-public-key binding. 4. Validate the Intel TDX node evidence according to the public contract. 5. Keep the conclusion within the supported boundary. The bounded successful conclusion is TDX NODE VERIFIED. It does not verify the workload image, source code, runtime arguments, or operator exclusion. ### Retry and recover requests Use a stable Idempotency-Key before sending a request that may be retried. A retry must converge the original request and billing state rather than create another provider execution. Direct-mode recovery can look up request and billing state, but it 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 feature gate is not generally open. ### Handle Credits Credits purchase and the device wallet are Beta / rollout pending. 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. Protect the proof and private-key material as spending authority. Encrypted device storage, backup, recovery, funding, and account-balance conversion remain subject to rollout gates. ### Screen privacy Optional device-local App Screen Lock with a 4-digit or 6-digit passcode is Coming Soon. It is a screen-privacy control and does not replace the recovery key or add a new Credits-encryption layer. ### Video and media Video generation APIs and media-capable routes are Coming Soon. They remain under integration and are not generally available. Do not build a production dependency on /v1/videos routes yet. ### Availability labels Available means the live service or catalog exposes the capability. 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.