> ## Documentation Index
> Fetch the complete documentation index at: https://docs.archal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What is an Archal clone

> Archal clones are service-shaped test environments for agents, ranging from stateful behavioral clones to architecture previews with narrower evidence-backed surfaces.

## 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](/clones/apify): actors, runs, datasets, key-value stores, and request queues.
* [Datadog](/clones/datadog): metrics, logs, monitors, dashboards, SLOs, synthetics, incidents, teams, users, and service definitions.
* [GitHub](/clones/github): repos, issues, PRs, branches, files, commits, actions, releases, and code scanning.
* [Discord](/clones/discord): guilds, channels, messages, reactions, threads, webhooks, commands, and interaction responses.
* [HubSpot](/clones/hubspot): CRM contacts, companies, deals, tickets, and engagements.
* [Slack](/clones/slack): channels, messages, threads, reactions, users, files, admin, and apps platform workflows.
* [Stripe](/clones/stripe): customers, products, prices, payments, invoices, subscriptions, disputes, and connect.
* [Jira](/clones/jira): issues, projects, boards, sprints, fields, workflows, service desk, and automation.
* [Linear](/clones/linear): issues, projects, teams, cycles, initiatives, roadmaps, labels, and views.
* [Supabase](/clones/supabase): SQL queries, tables, migrations, extensions, edge functions, and branches.
* [Google Workspace](/clones/google-workspace): Gmail, Calendar, Drive, Sheets, and Contacts.
* [Ramp](/clones/ramp): cards, funds, transactions, reimbursements, bills, approvals, and travel.
* [Customer.io](/clones/customerio): campaigns, broadcasts, transactional email, triggers, segments, customers, and message delivery.
* [Sentry](/clones/sentry): organizations, projects, issues, latest events, stack traces, and releases.
* [OwnerRez](/clones/ownerrez): properties, bookings, guests, quotes, financial reads, tags, fields, and webhook subscriptions.
* [PriceLabs](/clones/pricelabs): listings, price overrides, neighborhood data, rate plans, and reservations.
* [Tavily](/clones/tavily): search, extract, crawl, map, research, usage, and API key operations.
* [Unipile](/clones/unipile): LinkedIn and email messaging, accounts, and chats.
* [Webflow](/clones/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](/clones/calcom): event types, schedules, availability slots, and the booking lifecycle.
* [ClickUp](/clones/clickup): teams, spaces, folders, lists, tasks, comments, tags, time tracking, and checklists.
* [GitLab](/clones/gitlab): projects, branches, commits, issues, merge requests, pipelines, labels, milestones, releases, and webhooks.

Need something else? Email [us](mailto:founders@archal.ai).

## Compatibility matrix

Not every clone supports every workflow.

Not every clone supports MCP. Clones with MCP support: Cal.com, ClickUp,
Discord, GitHub, GitLab, Google Workspace, Jira, Linear, Ramp, Slack, Stripe,
and Supabase. The rest expose a REST or API surface only. 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, HubSpot,
Slack, Stripe, Jira, Linear, Supabase, Google Workspace, OwnerRez, PriceLabs,
Tavily, 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`](/guides/run-with-agent): run a scenario or task against clones
  and get a satisfaction score.
* [`archal clone`](/guides/clone-sessions): start persistent clones for
  debugging or manual integration work.
* [`archal/vitest`](/guides/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.