# AX Check: vestra.ai Checked 2026-09-19. Pricing is clear, but docs leave agents guessing All four plan prices and credit limits are stated openly on the pricing page, but no quickstart, install steps, or API/MCP docs were found for agents to act on. ## Onboarding needs a login ## Coding sessions All three independent coding sessions completed and found the pricing page. Two sessions read out the Lite/Pro/Max/Ultra tiers with credit and resource limits; one instead reported no fixed product price and detailed underlying infrastructure cost drivers. ### DeepSeek V4 Pro [View public run](https://agents.withgauge.com/p/runs/bf0333bc-42f9-4250-97d2-3811dc0dd6ff) · [Read transcript](https://www.ax-check.com/vestra.ai/sessions/deepseek.json) Final output states there is no published product price and instead breaks down real cost drivers (self-hosting, NEAR gas, 1Click bridging fees, Pagoda relayer/FastAuth costs) as the assumptions behind that answer, rather than inventing a number. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No credential acquisition occurred. The agent found only a self-hosted Vestra codebase (Express API + React app) requiring local dev servers, and a separate hosted 1Click API that needs a manually-requested JWT plus a NEAR wallet, none of which the agent could obtain in-session. It explicitly stopped rather than start local services or fabricate credentials, so neither credential retrieval nor an authenticated hosted operation was demonstrated. Event 72: ```text There is **no published npm SDK** (`npm view vestra` → 404/unpublished), no public hosted REST base URL, and I have **no credentials** in this environment (no 1Click JWT, no NEAR key, no relayer URL). ``` Event 72: ```text It requires **manual credential onboarding** I can't perform (1Click JWT request, NEAR account/wallet). ``` Event 72: ```text So plainly: **there is no hosted product workflow I can act on here, and I'm stopping rather than fabricate an example or spin up local services.** ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No published Vestra package or hosted API endpoint**: Product behavior/naming ambiguity: npm registry has no 'vestra' package, and the only matching product found via web search was a GitHub repo (Vestra-one/core), not a hosted SDK. The candidate domains vestra.xyz and vestra.io are parked GoDaddy sale pages, and api.vestra.xyz returned a 502, so there is no reachable hosted API to call. Event 7: ```text npm error 404 Unpublished on 2026-07-25T12:27:09.906Z npm error 404 npm error 404 'vestra' is not in this registry. ``` Event 60: ```text You don't have permission to access "http://forsale.godaddy.com/forsale/vestra.xyz?" on this server. ``` Event 44: ```text -- https://api.vestra.xyz 502 https://api.vestra.xyz/ ``` - **Quickstart requires local service stacks**: Product design: the only documented developer workflow for Vestra is cloning the repo and running two local dev servers (vestra-api on port 3032 and vestra-app on port 5173) with in-memory storage. This conflicts with the session's instruction to avoid starting local service stacks, so the agent could not proceed. Event 25: ```text Listens on `http://0.0.0.0:3032` by default. Set `PORT` to override. ``` Event 34: ```text cd vestra-app npm install cp .env.example .env # set VITE_API_URL and optional vars (see Environment) npm run dev ``` Event 72: ```text It requires **local service stacks** (the API and app dev servers) — which you told me not to start. ``` - **Real payment functionality gated behind manual credential request**: Missing credentials: actual cross-chain payment execution goes through the hosted 1Click API, which requires a JWT that must be manually requested from a partner portal, plus a connected NEAR wallet — neither obtainable by the agent in this session. Event 65: ```text 1Click API: JWT required for getQuote, submitDepositTx, getExecutionStatus. Request at https://partners.near-intents.org ``` Event 72: ```text Payments themselves run through **1Click** (`https://1click.chaindefuser.com`), which is hosted **but requires a JWT you must manually request** at `partners.near-intents.org` (`VITE_ONE_CLICK_JWT`), plus a connected **NEAR wallet** and optional **Pagoda relayer URL**. ``` #### Suggested Changes - **Publish a hosted sandbox or demo instance of the Vestra API**: Add a publicly reachable hosted instance (with a documented base URL) of vestra-api so developers can test session/contacts/preferences endpoints without running local dev servers; verify by curling the documented endpoint from an external environment and confirming a 200 response. Event 25: ````text ## Run ```bash npm install npm run dev ``` Listens on `http://0.0.0.0:3032` by default. ```` Event 44: ```text -- https://api.vestra.xyz 502 https://api.vestra.xyz/ ``` - **Add a pricing page or pricing section to the repo README**: Add pricing information (hosting costs, 1Click/bridging fee structure, gas cost guidance) to the top-level README or docs folder so developers evaluating the product do not have to infer costs from infrastructure references; verify by confirming a 'Pricing' heading exists in README.md or docs/ and lists concrete fee or cost figures. Event 72: ```text I found **no published pricing for this product.** There's no pricing page or tier description in the repo/docs ``` - **Provide a self-service or sandbox path for the 1Click JWT**: Link a self-service signup or sandbox token flow for the 1Click JWT directly in vestra-app/.env.example instead of only a manual partner request, so automated or first-time developer workflows are not blocked; verify by confirming a documented endpoint or signup link in .env.example that returns a usable token without human intervention. Event 65: ```text 1Click API: JWT required for getQuote, submitDepositTx, getExecutionStatus. Request at https://partners.near-intents.org ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/b285b566-c6de-4e88-a896-d5cad8a59e7e) · [Read transcript](https://www.ax-check.com/vestra.ai/sessions/kimi.json) Final output states credit-based tiers (Lite $19/mo, Pro $97/mo, Max $197/mo, Ultra $497/mo, custom $4,000/mo) with named assumptions (credits/mo, RAM, storage, autonomy level, free-tier 1,000 credits, annual discount), sourced from vestra.ai/pricing at seq 44. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: The agent never obtained real product credentials or performed any authenticated operation. It only crawled public marketing pages, tried guessed developer paths (all 404), and confirmed no SDK/package existed. It stopped before signup or API key acquisition, so onboarding was never attempted, let alone verified. Event 62: ```text {"message":"Route GET:/ not found","error":"Not Found","statusCode":404} ``` Event 64: ```text No public API surface**: `api.vestra.ai` exists but is the app's internal backend (unversioned, no docs, no OpenAPI spec). `/docs`, `/developers`, and `/sdk` all 404. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public API, SDK, or docs exist for Vestra**: Product behavior, not agent error or missing credentials: the agent methodically checked PyPI, npm, GitHub, and the vestra.ai site itself for /docs, /api, /developers, /sdk paths and an api.vestra.ai backend, all returning 404 or unpublished-package results. There is no documented developer surface to build against, so the task could not proceed regardless of credentials. Event 15: ```text {'time': '2026-07-25T12:27:09.906Z', 'versions': ['0.1.0', '0.1.1', '0.1.2', '0.1.3', '0.1.4', '0.1.5', '0.1.6', '0.1.7', '0.1.8', '0.1.9']} ``` Event 40: ```text == /docs 404 ...== /api 404...== /developers 404...== /sdk 404 ``` Event 62: ```text {"message":"Route GET:/ not found","error":"Not Found","statusCode":404} ``` Event 64: ```text No developer primitives**: no API keys, webhooks, CLI, or developer-exposed MCP server in the product handbook. ``` #### Suggested Changes - **Publish a public API or SDK reference if one exists**: If Vestra has an internal API at api.vestra.ai, publish an OpenAPI spec or docs page (e.g., at vestra.ai/docs or vestra.ai/api) so external developers are not met with 404s; verify by re-running the same path checks (/docs, /api, /developers, /sdk) and confirming a 200 response with real documentation content. Event 40: ```text == /docs 404 ...== /api 404...== /developers 404...== /sdk 404 ``` - **Republish or remove the abandoned npm 'vestra' package**: The npm package named 'vestra' was unpublished mid-2026, which could mislead developers searching package registries; either republish an official SDK under this name or add a note/redirect pointing to the real product site, and confirm by checking https://registry.npmjs.org/vestra returns an active, current package. Event 15: ```text {'time': '2026-07-25T12:27:09.906Z', 'versions': ['0.1.0', '0.1.1', '0.1.2', '0.1.3', '0.1.4', '0.1.5', '0.1.6', '0.1.7', '0.1.8', '0.1.9']} ``` ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/7605a14e-ccef-49a9-b51b-314264f76deb) · [Read transcript](https://www.ax-check.com/vestra.ai/sessions/qwen.json) Final output gives a full pricing table (Lite/Pro/Max/Ultra, $19-$497) tied to explicit assumptions: credits/mo, machine RAM, storage, autonomy tier, plus free-start 1,000 credits and annual -10% discount, sourced from the live /pricing page (seq 31). #### End-to-end onboarding - **Onboarding needs a login**: Agent found no SDK, API, CLI, or public docs for Vestra — only a marketing site behind an invite-gated private beta login and a Tauri desktop GUI shell. It never obtained credentials (no signup/invite flow was accessible without a human) and consequently never performed any authenticated operation against the product. Session ended in a stop-and-report per the seed prompt's instruction to halt if there is no actionable developer workflow. Event 18: ```text https://vestra.dev -> 000 https://www.vestra.io -> 200 https://docs.vestra.dev -> 000 https://vestra.ai -> 200 ``` Event 28: ```text /pricing -> 200 /docs -> 404 /developers -> 404 /api -> 404 /sdk -> 404 /docs/api -> 404 /status -> 404 /changelog -> 404 /openapi.json -> 404 ``` Event 40: ```text https://api.vestra.ai -> 404 https://developers.vestra.ai -> 000 https://vestra.ai/api/health -> 404 ``` Event 42: ```text Everything lives behind an invite-gated login and a GUI/desktop shell. I can't provision an account, obtain credentials, issue a request, or verify a result. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public API, SDK, or CLI exists for Vestra**: Product behavior, not agent error or missing credentials: the agent systematically checked npm, PyPI, common API/docs subdomains, and in-page links, and found no programmatic entry point at all. Vestra is a GUI-only, private-beta product accessed through login or a desktop shell, with credentials injected at the infra layer and never exposed to any agent/model. This matches the seed prompt's explicit stop condition for 'no developer workflow.' Event 12: ```text npm error 404 npm error 404 'vestra' is not in this registry. ``` Event 17: ```text ERROR: No matching distribution found for vestra ``` Event 28: ```text /docs -> 404 /developers -> 404 /api -> 404 /sdk -> 404 /docs/api -> 404 /status -> 404 /changelog -> 404 /openapi.json -> 404 ``` Event 39: ```text The model never sees a password or an API key: credentials are injected at the infrastructure layer ``` - **Access gated behind invite / Calendly call, no self-serve signup**: Product design choice: the product is explicitly in private beta and requires either an invite or booking an onboarding call, which is a normal human-login/access requirement rather than a product defect. This alone kept the agent from creating an account or obtaining any credentials. Event 33: ```text How do I get in? Vestra is in private beta. Join with an invite or book a call, and start with 1,000 credits on the house. ``` Event 27: ```text href="https://calendly.com/keshav-vestra/vestra-onboarding" ``` #### Suggested Changes - **Publish a developer/API section even if minimal**: On vestra.ai, add a /developers or /api page (currently 404) describing whether any programmatic access exists, even if it's 'GUI only, no API today.' Verify by re-requesting the same paths the agent tried (/docs, /developers, /api, /sdk, /openapi.json) and confirming they resolve instead of 404. Event 28: ```text /docs -> 404 /developers -> 404 /api -> 404 /sdk -> 404 /docs/api -> 404 /status -> 404 /changelog -> 404 /openapi.json -> 404 ``` - **Clarify in marketing copy that Vestra is GUI/desktop-only with no SDK**: The handbook and pricing pages describe agents, credentials, and 'Bash'/'Nami' engines in technical detail without stating plainly that there is no external API/SDK for developers to integrate against. Adding a short line to the handbook or FAQ (e.g., near the 'Do I need to be technical?' FAQ entry) stating there's no public API would save developer-audience readers from the same dead-end search the agent performed. Event 33: ```text Do I need to be technical? No. If you can say what you want, you can delegate it. ``` Event 39: ```text credentials are injected at the infrastructure layer, used for the ``` ### Task given to each agent Help me build a simple example using Vestra. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: D · 34/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown request; no Markdown representation served. ``` - **Failed** — llms.txt provides an actionable documentation index ```text llms.txt exists but links only homepage, blogs, policies, login — no docs or API index. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt groups content under About, How it works, Blog, Pricing, Policies, Optional headings. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text llms.txt mentions AGENTS.md and agent-permissions.json but no API, MCP, or skills surfaces. ``` - **Skipped** — A compact guide representation exists ```text No compact agent guide fetched; only llms.txt index and homepage were retrieved. ``` - **Skipped** — A focused guide is directly retrievable ```text No standalone Markdown guide or negotiated Markdown page was fetched for Vestra. ``` - **Skipped** — Equivalent instructions fit a token budget ```text No compact guide was retrieved, so token budget cannot be measured. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown unsupported, so link preservation across formats is unassessed. ``` - **Skipped** — The compact guide is independently actionable ```text No compact agent guide fetched; only llms.txt index and homepage were retrieved. ``` - **Pass** — Install and next-step links resolve ```text Homepage install/next-step links (login, pricing, handbook) fetched successfully. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text No docs or quickstart pages fetched; only llms.txt, login and pricing links available. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI guide fetched; llms.txt lists no install commands. ``` - **Skipped** — Code examples are available without interaction ```text No docs or code example pages fetched for Vestra. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text No API or developer docs fetched; only Google sign-in on login page. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page renders all four plan prices and features as static text, no interaction needed. ``` - **Pass** — Prices are stated, not gated ```text Lite $19, Pro $97, Max $197, Ultra $497 monthly stated openly; enterprise from $4,000. ``` - **Pass** — Pricing units and limits are explicit ```text Credits per month (2,000/10,000/20,000/50,000), RAM and storage listed per plan. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4 Pro: Final output states there is no published product price and instead breaks down real cost drivers (self-hosting, NEAR gas, 1Click bridging fees, Pagoda relayer/FastAuth costs) as the assumptions behind that answer, rather than inventing a number. Kimi K3: Final output states credit-based tiers (Lite $19/mo, Pro $97/mo, Max $197/mo, Ultra $497/mo, custom $4,000/mo) with named assumptions (credits/mo, RAM, storage, autonomy level, free-tier 1,000 credits, annual discount), sourced from vestra.ai/pricing at seq 44. Qwen 3.8 Max: Final output gives a full pricing table (Lite/Pro/Max/Ultra, $19-$497) tied to explicit assumptions: credits/mo, machine RAM, storage, autonomy tier, plus free-start 1,000 credits and annual -10% discount, sourced from the live /pricing page (seq 31). This behavioural item does not affect the fast grade. ``` ### Activation - **Skipped** — An API reference or OpenAPI spec is reachable ```text No API reference or OpenAPI spec found in fetched Vestra pages. ``` - **Skipped** — An MCP server is documented and well-formed ```text No MCP server documentation found in fetched Vestra pages. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in fetched Vestra pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK package or registry result supplied for Vestra. ``` - **Skipped** — Agent skills are published ```text No agent skills published in fetched Vestra pages. ``` [Full report data](https://www.ax-check.com/vestra.ai/report.json)