Skip to main content

​
What is a clone?

A clone is a service-shaped test environment for agents. Mature clones keep objects, relationships, and constraints close enough to the real service that your agent can use normal tools without touching production. Architecture previews are narrower: they may combine stateful overlays with fixture or recording-backed compatibility while the service-specific behavior model is still being built. Use clones when correctness depends on state changing across several calls: create an issue, read it back, comment on it, close it, and verify the final state without touching the real service.

​
Available clones

Pick the service your agent already talks to.
  • Apify: actors, runs, datasets, key-value stores, and request queues.
  • Datadog: metrics, logs, monitors, dashboards, SLOs, synthetics, incidents, teams, users, and service definitions.
  • GitHub: repos, issues, PRs, branches, files, commits, actions, releases, and code scanning.
  • Discord: guilds, channels, messages, reactions, threads, webhooks, commands, and interaction responses.
  • Firecrawl: scraping, crawling, mapping, search, and extraction.
  • HubSpot: CRM contacts, companies, deals, tickets, and engagements.
  • Slack: channels, messages, threads, reactions, users, files, admin, and apps platform workflows.
  • Stripe: customers, products, prices, payments, invoices, subscriptions, disputes, and connect.
  • Jira: issues, projects, boards, sprints, fields, workflows, service desk, and automation.
  • Linear: issues, projects, teams, cycles, initiatives, roadmaps, labels, and views.
  • Supabase: SQL queries, tables, migrations, extensions, edge functions, and branches.
  • Google Workspace: Gmail, Calendar, Drive, Sheets, and Contacts.
  • Ramp: cards, funds, transactions, reimbursements, bills, approvals, and travel.
  • SendGrid: mail send, contacts, lists, templates, and stats.
  • Customer.io: campaigns, broadcasts, transactional email, triggers, segments, customers, and message delivery.
  • Sentry: organizations, projects, issues, latest events, stack traces, and releases.
  • OwnerRez: properties, bookings, guests, quotes, financial reads, tags, fields, and webhook subscriptions.
  • PriceLabs: listings, price overrides, neighborhood data, rate plans, and reservations.
  • Tavily: search, extract, crawl, map, research, usage, and API key operations.
  • Telegram: bot messages, chats, updates, and webhooks.
  • Twilio: messages, calls, phone numbers, and verifications.
  • Unipile: LinkedIn and email messaging, accounts, and chats.
  • Webflow: sites, pages, CMS collections, items, assets, forms, and webhooks.

​
Previews

These clones are accurate on what they implement but coverage is still pending, so the surface does not yet span the full API.
  • Cal.com: event types, schedules, availability slots, and the booking lifecycle.
  • ClickUp: teams, spaces, folders, lists, tasks, comments, tags, time tracking, and checklists.
  • GitLab: projects, branches, commits, issues, merge requests, pipelines, labels, milestones, releases, and webhooks.
  • Typeform: forms, responses, workspaces, themes, and webhooks.
  • WooCommerce: products, customers, orders, coupons, categories, payment gateways, shipping zones, and taxes.
Need something else? Email us.

​
Compatibility matrix

Not every clone supports every workflow. Every listed clone supports MCP. Stateful fidelity depends on the clone’s declared surface: some clones are behavioral, while Architecture Preview clones are still replay-backed or overlay-limited. Clones with REST or API fidelity: Apify, GitHub, Discord, Firecrawl, HubSpot, Slack, Stripe, Jira, Linear, Supabase, Google Workspace, OwnerRez, PriceLabs, SendGrid, Tavily, Telegram, Twilio, Unipile, Webflow, and Datadog. Clones with route mode for both archal run and archal/vitest: GitHub, Discord, Slack, Stripe, Jira, Linear, Supabase, Google Workspace, and Ramp’s primary API domain, plus Apify, Tavily, and Datadog. Use explicit base URLs for GitHub, Discord, Slack, Stripe, Jira, Linear, Supabase, Google Workspace, Apify, Tavily, Datadog, and Ramp’s primary API domain. Ramp is MCP-first outside explicit base URL runs. Route mode lets an existing agent call real service domains, such as api.github.com, while Archal routes that traffic to the clone. Use explicit base URLs when you want the simplest integration path.

​
Three ways to use clones

  • archal run: run a scenario or task against clones and get a satisfaction score.
  • archal clone: start persistent clones for debugging or manual integration work.
  • archal/vitest: use supported hosted clones inside your existing Vitest test suite. Route mode currently supports Discord, GitHub, Google Workspace, Jira, Linear, Ramp’s primary API domain, Slack, Stripe, Supabase, Apify, Tavily, and Datadog.