Services

Services are simulated versions of the external APIs and SaaS platforms your agent integrates with. Your agent makes real HTTPS calls to real domains — they’re transparently routed to intelligent mocks inside the simulation container. No code changes needed.

Available Services

Service	Config Name	Category
DXC Hogan	`hogan`	Core Banking
Stripe	`mcp/stripe`	Payments
Salesforce	`salesforce`	CRM & Support
HubSpot	`hubspot`	CRM & Support
Zendesk	`zendesk-support`	CRM & Support
ServiceNow	`servicenow`	CRM & Support
PagerDuty	`pagerduty`	CRM & Support
Jira	`atlassian/jira`	Collaboration
Confluence	`atlassian/confluence`	Collaboration
Slack	`slack`	Collaboration
Google Calendar	`google/calendar`	Collaboration
Google Drive	`google/drive`	Collaboration
Microsoft Graph	`microsoft/graph`	Collaboration
Azure DevOps	`microsoft/devops`	Collaboration
Oracle FSCM	`oracle/fscm`	Enterprise
Shopify Storefront	`mcp/shopify-storefront`	Commerce
Shopify Customer	`mcp/shopify-customer`	Commerce
PostgreSQL	`postgres`	Infrastructure
Twilio	`twilio`	Infrastructure
Google Auth	`google/auth`	Auth
Microsoft Auth	`microsoft/auth`	Auth
Atlassian Auth	`atlassian/auth`	Auth
Email	`email`	Channels

MCP Servers (Drop-In Simulation)

Services prefixed with mcp/ are Model Context Protocol servers. Veris provides drop-in simulation for any MCP server your agent uses. The pre-built ones (Stripe, Shopify Storefront, Shopify Customer) are ready out of the box, but any MCP server can be simulated.

Always Running (Auto-Injected)

These services start automatically in every simulation — you don’t need to declare them:

Service	Purpose
Engine	Simulation orchestrator — seeds services, manages lifecycle
Actor	Simulated user — role-plays personas and pursues objectives
LLM Proxy	Proxies your agent’s LLM calls for tracing, cost tracking, and token counting

Configuration Example

.veris/veris.yaml


services:
  - name: google/calendar
    dns_aliases:
      - www.googleapis.com
      - calendar.google.com
 
  - name: salesforce
    dns_aliases:
      - myorg.my.salesforce.com
 
  - name: mcp/stripe
 
  - name: postgres
 
  - name: atlassian/jira
    dns_aliases:
      - myorg.atlassian.net

PostgreSQL

The PostgreSQL service is unique — it provides a real PostgreSQL database (not an LLM mock). During the seed phase, the LLM generates SQL INSERT statements based on the scenario context. Your agent queries it using standard SQL.

If your agent needs a specific schema, include it in your Docker image:


COPY schemas /agent/schemas

Schema files are applied before seeding.

Using the Console

On the Overview page, the simulated services panel shows all available services grouped by category. When viewing an Environment, the configured services are displayed on the environment card.

To change which services are enabled, update your veris.yaml and push a new image.