Every twin, and what it holds.
A twin is a stateful simulation of one service your code calls. It speaks the interface your driver or SDK already speaks, and it remembers what happened between calls, so writing a row and reading it back, or waiting on a webhook, is a real test rather than a canned response.
34 services
| Twin | Category | Speaks | Holds state for |
|---|---|---|---|
| Stripe | Payments & finance | REST + webhooks | customers, payment intents, charges, refunds, subscriptions |
| Marqeta | Payments & finance | REST | cardholders, cards, GPA orders, transactions |
| Daraja (M-Pesa) | Payments & finance | REST + callbacks | STK push, B2C payments, transaction status, balance |
| Apache Fineract | Payments & finance | REST | clients, savings and loan accounts, transactions, schedules |
| QuickBooks Online | Payments & finance | REST + webhooks | customers, invoices, payments, bills, reports |
| Salesforce | CRM & sales | REST + SOQL | sObjects, records, composite batches, bulk jobs |
| HubSpot | CRM & sales | REST + webhooks | contacts, companies, deals, associations, pipelines |
| Attio | CRM & sales | REST + webhooks | objects, records, attribute history, lists, notes |
| Jira | Work management | REST | issues, comments, attachments, links, worklogs |
| Linear | Work management | GraphQL | issues, teams, users, projects, milestones |
| Asana | Work management | REST + webhooks | projects, tasks, subtasks, stories, custom fields |
| Notion | Docs & spreadsheets | REST + webhooks | pages, databases, blocks, properties, comments |
| Airtable | Docs & spreadsheets | REST + webhooks | records, base and field schema, comments, attachments |
| Figma | Design & creative | REST + webhooks | files, node trees, renders, comments, versions |
| Frame.io | Design & creative | REST | accounts, workspaces, projects, folders, webhooks |
| Autodesk APS | Design & creative | REST + OAuth | tokens, buckets, objects |
| Dropbox | Files & storage | REST + MCP | files, folders, sync cursors, revisions, shares |
| Google Drive | Files & storage | REST + webhooks + MCP | files, folders, permissions, comments, revisions |
| Gmail | Communication | REST + MCP | messages, threads, drafts, labels, attachments |
| Outlook Mail | Communication | Graph REST + webhooks | messages, folders, attachments, sends |
| Microsoft Teams | Communication | Graph REST + webhooks | teams, channels, chats, messages |
| Slack | Communication | Web API + Events API | channels, messages, threads, users, reactions |
| Google Calendar | Scheduling | REST + webhooks | calendars, events, recurrence, ACLs, free/busy |
| Outlook Calendar | Scheduling | Graph REST + webhooks | calendars, events, instances, attachments |
| Calendly | Scheduling | REST + webhooks | event types, availability, scheduled events, invitees |
| Acuity Scheduling | Scheduling | REST + webhooks | appointments, availability, clients, intake forms |
| GitHub | Developer tools | REST + webhooks | repos, branches, pull requests, issues, releases |
| Hugging Face | Developer tools | REST | models, datasets, Spaces, revisions, discussions |
| Google Identity | Identity | OAuth 2 + OIDC | auth codes, access and refresh tokens, JWKS |
| Microsoft Identity | Identity | OAuth 2 + OIDC | five grants, device codes, consent, logout |
| Adobe IMS | Identity | OAuth 2 + OIDC | auth codes, refresh tokens, userinfo, JWKS |
| Atlassian Identity | Identity | OAuth 2.0 3LO | auth codes, rotating refresh tokens |
| PostgreSQL | Infrastructure | Postgres wire protocol | schemas, tables, rows, transactions |
| Yente (OpenSanctions) | Compliance | REST | watchlist matches, datasets, entities, adjacency |
If you do not see a service you need, or you have internal proprietary systems, get in touch.
Request a service →No twin matches that.
Veris builds one from an API spec — talk to us about it.
How are Veris AI twins different?
Vendor-true
The same endpoints, status codes, webhook timing, and edge-case behavior as the service it mirrors. Maintained centrally, so when a vendor ships a change your tests track the service rather than a snapshot of it.
Stateful
Every twin remembers. Create a charge and the balance moves; transition a ticket and the SLA timer starts. A verifier can assert on what the code did to the world, not just on what came back.
Failure on cue
Outages, timeouts, rate limits, malformed payloads, and duplicate webhooks are configuration, not luck. The unhappy paths get tested because you can ask for them.
Seeded and resettable
Each twin starts from a seed you control, either your own fixtures or Veris-composed synthetic data, and resets to that exact baseline in milliseconds. A failing run reproduces instead of flaking.