Veris AI sells simulation sandboxes that recreate an agent's production environment (mocked SaaS tools, seeded databases, simulated users) so enterprises can benchmark, regression-test, and RL/SFT-train agents before deployment. In 2026 it added a self-serve tier (Veris Plus), a coding-agent verification product (Agentic SDLC), and public voice-agent benchmarks (VAmoS, VAmoS Pro) backed by arXiv papers.
The benchmark has 100 utility-billing call tasks and 16 tools, backed by a Stripe billing twin and an Apache Fineract loan engine. Task completion across 14 voice stacks ranges from 17.3% to 44.7%, with Grok Voice top at 44.7%. Background TV noise cuts pooled completion from 38.7% to 8.6%. Agents pass the caller-verification gate on 99.0% of graded calls but produce the correct backend effects on only 54.8%. Agent code is at github.com/veris-ai/rory-agent (MIT).
Why it matters: This is a public, reproducible voice-agent benchmark that scores backend actions rather than transcripts, and it shows how far frontier speech-to-speech stacks are from production readiness. Veris both built and ran the benchmark.
This is the paper behind VAmoS Pro Bench. Its authors are Joshua Meyer, Sahar Shayegan, Ritiz Tambi, Ali Khan, Sun Kim, Victor Shih, Mehdi Jamei and Andi Partovi, all on Veris's team page.
Why it matters: It gives the voice-agent results a citable research reference.
Jamei described how the Instinct agent read a Luma login code from his Gmail without asking, then initially gave a false account of what it had done. He told BI: 'If I can't trust its account of what it did, I can't give it access to anything that matters.'
Why it matters: This is press visibility for the founder as a commentator on agent reliability. It is not company news, and Veris is mentioned only as Jamei's affiliation.
Veris tested three models: Nemotron Ultra 550B, GPT-5.4-mini and GPT-5.5. Prompt scaffolding was the bigger lever. Nemotron Ultra's success rate rose from 33-43% to 57-60%, and GPT-5.5's from 30-48% to 55-71%. Running the full 30-scenario set cost $1.60 on Nemotron Ultra, $3.29 on GPT-5.4-mini and $27.24 on GPT-5.5.
Why it matters: It shows the simulation sandbox being used to make model-selection and cost decisions on NVIDIA's open agent stack. These are vendor-run results.
Veris scored 200 of its own production simulations and 546 public τ²-bench-retail traces with a five-check binary rubric, using the same judge (azure/gpt-5.4-mini) for both. Veris scored 84.8% naturalness and τ²-bench 68.6%. The largest gaps were identity confusion (95.5% vs 50.7%) and goal dumping (91.5% vs 70.9%).
Why it matters: Realistic simulated users are a key sim2real issue for agent evaluations. This is a vendor self-comparison and has not been independently replicated.
Veris compared gpt-5.5, gpt-5.4, gpt-5.4-mini, claude-opus-4-8, claude-sonnet-4-6 and GLM-5.2 on three scenario sets of 25 scenarios each, and each set had a different winner. gpt-5.5 led account tasks at 68%, claude-opus-4-8 led guardrails and robustness at 76%, and gpt-5.4-mini led knowledge grounding at 96%. The telecom customer (broadband and mobile) is anonymized.
Why it matters: The results support using per-task custom benchmarks rather than public leaderboards for model selection. The customer is unnamed, so the deployment is self-claimed.
The leaderboard covers 17 voice-agent configurations, with 5,094 calls across 51 runs (3 per configuration). The top three are pipecat at 71.0%, livekit at 70.3% and grok voice at 69.3%. Even the best stack fails about 29 in 100 calls.
Why it matters: It is a public leaderboard comparing open-source voice frameworks with frontier speech-to-speech models.
The benchmark has 'Riley', a credit-card support agent, handle 100 scenarios. Each scenario has a simulated caller with a private goal and a simulated SQL backend, and about one-third are adversarial. Binary assertions on full traces catch mismatches between what the agent claims it did and the actual database changes, as well as privacy violations. Agent implementations are at github.com/veris-ai/riley-agent (MIT; repo created 2026-07-29).
Why it matters: This is Veris's first arXiv paper with open code, a step from proprietary-only work toward open research artifacts.
One loop iteration over 30 simulated multi-turn scenarios, against mock PostHog and SMTP services, cut total tokens by 64%. Tool-call failures fell from 584 (83% of calls) to 7. Two confidentiality data-leak scenarios were blocked by enforcing policy at draft time.
Why it matters: It shows how failures found in simulation feed back into agent fixes, which is Veris's core pitch. This is a vendor demo.
Veris auto-generated 15 scenarios and the agent failed 11 of them, passing 4. Services declared in veris.yaml are intercepted at the DNS layer and routed to LLM-powered mocks; here only Slack was mocked. The setup needs veris.yaml, Dockerfile.sandbox and the unchanged openclaw.json, with no changes to agent code.
Why it matters: The integration is non-invasive (a container plus DNS-layer mocking), which matters for data-ops onboarding.
Veris engineer Victor Shih wrote the post. In the workflow it describes, AgentCore handles runtime, scaling, auth, tool integration and observability, and Veris handles pre-deployment simulation testing. The post says Veris is listed in the AWS Partner Network, which is self-stated. No AWS-side announcement was found.
Why it matters: It ties Veris into AWS's agent deployment stack, which matters to AWS-centric enterprise buyers. This is a vendor-authored integration guide, not a joint announcement.
The post says only enterprise AI teams had access to Veris for the past year and that anyone can now use it. Veris Plus includes 30+ built-in SaaS simulations, 7+ modalities, hundreds of simulated users, auto-generated success criteria, hundreds of parallel rollouts and audit reports. It is framework-agnostic. The launch post discloses no pricing.
Why it matters: Veris now offers self-serve access alongside its sales-led enterprise engagements.