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.

Don’t see a service you need? Reach out about enterprise support — we can add coverage for additional APIs and MCP servers as part of our enterprise offering.

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

Full schema for the services block (fields, config, dns_aliases): veris.yaml → Services.

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

Available services

Service	Config name	Category
Atlassian Auth	`atlassian/auth`	Auth
Google Auth	`google/auth`	Auth
Intuit Auth	`intuit/auth`	Auth
Microsoft Auth	`microsoft/auth`	Auth
Bloomberg	`bloomberg`	Banking
Bloomberg MCP (Terminal)	`mcp/bloomberg-terminal`	Banking
DXC Hogan	`hogan`	Banking
ION Markets	`ion`	Banking
ION MCP	`mcp/ion`	Banking
LSEG Analytics	`lseg-analytics`	Banking
OpenSanctions	`opensanctions`	Banking
OSTTRA	`osttra`	Banking
OSTTRA MCP	`mcp/osttra`	Banking
Parameta Solutions	`parameta`	Banking
SWIFT gpi	`swift`	Banking
TransFICC	`transficc`	Banking
Email	`email`	Channels
ClawHub	`clawhub`	Developer Tools
GitHub	`github`	Developer Tools
Azure DevOps	`microsoft/devops`	Collaboration
Confluence	`atlassian/confluence`	Collaboration
Google Calendar	`google/calendar`	Collaboration
Google Docs	`google/docs`	Collaboration
Google Drive	`google/drive`	Collaboration
Jira	`atlassian/jira`	Collaboration
Microsoft Graph	`microsoft/graph`	Collaboration
Slack	`slack`	Collaboration
Shopify Customer	`mcp/shopify-customer`	Commerce
Shopify Storefront	`mcp/shopify-storefront`	Commerce
Close	`close`	CRM & Support
HubSpot	`hubspot`	CRM & Support
Outreach	`outreach`	CRM & Support
Marketo	`marketo`	CRM & Support
PagerDuty	`pagerduty`	CRM & Support
Salesforce	`salesforce`	CRM & Support
ServiceNow	`servicenow`	CRM & Support
Zendesk	`zendesk-support`	CRM & Support
Oracle FSCM	`oracle/fscm`	Enterprise
QuickBooks Online	`intuit/quickbooks-online`	Enterprise
Epic FHIR	`epic/fhir`	Healthcare
Datadog	`datadog`	Infrastructure
Elasticsearch	`elastic`	Infrastructure
Kubernetes	`kubernetes`	Infrastructure
PostgreSQL	`postgres`	Infrastructure
Splunk	`splunk`	Infrastructure
Twilio	`twilio`	Infrastructure
Plaid	`plaid`	Payments
Stripe	`mcp/stripe`	Payments
Zillow	`zillow`	Real Estate
Vertex AI Search	`google/vertex-search`	Search & Research
you.com	`you`	Search & Research

MCP servers

Services prefixed with mcp/ are Model Context Protocol servers. Stripe, Shopify Storefront, and Shopify Customer are pre-built and ready to drop in. Coverage for additional MCP servers is available via enterprise support.

mcp/bloomberg-terminal is different in kind: it is the community Bloomberg MCP server (MIT), vendored unmodified and run against the bloomberg mock through a blpapi-compatible HTTP shim. Your agent exercises the real third-party server, not a Veris reimplementation of it. It exposes a wave-1 subset of that server’s tools by default; set BLOOMBERG_MCP_TOOLS to choose a different set, or to an empty string for all of them.

mcp/ion and mcp/osttra wrap the ion (FX order management) and osttra (post-trade confirmation) mocks with the vendor’s reads plus a deliberate, minimal write surface: order create/cancel on ION and confirmation submit on OSTTRA — the writes an MCP-exclusive agent cannot work without. Each write is annotated honestly (cancel_order is destructive and idempotent on a replayed cancelId; create_order and submit_confirmation are non-idempotent on an unguarded retry, with the clientOrderId / idempotency-key discipline taught in the tool description), and everything else the specs document — affirm/dispute/amend/cancel on OSTTRA, the raw event-bus verbs, the token endpoint — remains excluded by a fail-closed catch-all. mcp/osttra also handles OAuth internally (no token tool) and collapses OSTTRA’s four-step event-bus protocol — subscribe, poll, redeem out-of-band chunks, acknowledge — into a single check_confirmation_events call, so a cursor can never be advanced past work that was not done.

The three service-backed MCP servers (mcp/bloomberg-terminal, mcp/ion, mcp/osttra) auto-attach their backing service: declaring only the mcp/* entry in veris.yaml boots, DNS-aliases, health-checks, seeds and snapshots the backing mock (bloomberg, ion, osttra) as if it had been declared too. The MCP servers themselves are stateless and never receive seed briefs — scenario seeding always targets the backing service.