icon of Archal

Archal

archal.ai

Stateful API sandboxes for testing AI agents

Visit websiteOpens in a new window
image of ArchalVisit website

What is Archal?

Archal is a testing sandbox platform for AI agents and API integrations. It provides isolated, time-bounded runtimes containing one or more stateful environments that behave like the APIs used in production. Each environment exposes familiar REST or MCP interfaces, retains mutations for the life of the sandbox, and can return to its declared starting state.

Archal states that each environment is an independently built simulation of the service it represents, not the provider's live service. Environment traffic is routed to Archal-managed implementations rather than your production accounts, and individual environment profiles document any exceptional dependency or behavior. Archal notes it is not affiliated with or endorsed by the providers shown, and trademarks belong to their owners.

How to use Archal?

  1. Sign up for an account. New accounts receive $5 after verified signup and another $15 when the first sandbox is ready; no card is required for self-serve use.
  2. Create a sandbox with one or more environments and a known starting state.
  3. Receive isolated REST and MCP endpoints as each environment starts.
  4. Call the environments using familiar API paths, payloads, and tools.
  5. Inspect requests, responses, mutations, timing, and usage together.
  6. Reset to restore every environment in the sandbox to its declared baseline.

A single Archal API key creates and manages every sandbox and environment. Calls share one gateway while each environment keeps the paths, methods, payloads, and response shapes your existing code expects. Archal also offers a setup prompt that can be pasted into Claude Code, Codex, Cursor, or Devin to start secure signup and install five verified skills.

Core features of Archal

Isolated sandboxes

Each sandbox is an isolated, time-bounded runtime that can hold one or more stateful API environments. Multiple environments in one sandbox each receive their own endpoint and readiness state.

Stateful environments

Changes persist between calls for the life of the sandbox and can be reset to the same starting point. State behavior varies by environment and operation; available environments have a supported capability profile, and environments in progress remain callable only where their documented behavior permits it.

Single API key

One Archal API key manages every sandbox and environment. Calls share one gateway while each environment keeps its expected paths, methods, payloads, and response shapes.

REST and MCP endpoints

Environments are available over REST, and some also over MCP.

Inspection and reset

Sandboxes let you see requests, responses, mutations, timing, and usage together, then restore every environment to its declared baseline.

Supported environments

Available environments include:

  • GitHub: Repos, issues, pull requests, branches, and commits. REST + MCP.
  • Linear: Issues, projects, teams, cycles, and workflows. REST + MCP.
  • Slack: Channels, messages, threads, users, and reactions. REST + MCP.
  • Supabase: SQL, migrations, logs, branches, and project metadata. REST + MCP.
  • Apify: Actors, runs, datasets, key-value stores, and request queues. REST.
  • Cal.com: Event types, schedules, availability slots, bookings, calendars, and webhooks. REST + MCP.
  • ClickUp: Teams, spaces, folders, lists, tasks, comments, tags, time tracking, and checklists. REST + MCP.
  • Customer.io: Messaging automation across campaigns, broadcasts, transactional email, segments, customers, and message delivery. REST.

Additional selectable environments shown include Datadog, Discord, GitLab, Google Workspace, HubSpot, Jira, OR, OwnerRez, PriceLabs, Ramp, Sentry, Stripe, Tavily, Unipile, and Webflow.

Coding agent setup

The setup prompt detects whether you use Claude Code, Codex, Cursor, or Devin, and installs the verified Agent Skills bundle. It is instructed not to modify application code or start an environment during setup.

Use cases of Archal

Agent harness testing

Gives every test run an isolated sandbox where changes persist across tool calls and then reset to the same baseline.

Integration testing

Gives every branch or CI job its own sandbox without shared test accounts, rate limits, or dirty state.

Agent training and reinforcement learning

Gives every rollout a sandbox with the same starting state while changes persist through the episode.

Archal is intended for agent developers, connectors teams, and integration engineers.

Frequently asked questions about Archal

What is a testing sandbox?

An Archal sandbox is an isolated, time-bounded runtime containing one or more stateful environments. Each environment exposes familiar REST or MCP interfaces, retains mutations for the life of the sandbox, and can return to its declared starting state.

Do I need a different API for every environment?

No. One Archal API key creates and manages every sandbox and environment. Calls share one gateway while each environment keeps the familiar paths, methods, payloads, and response shapes existing code expects.

How stateful are the environments?

State behavior varies by environment and operation. Available environments have a supported capability profile; environments in progress remain callable only where their documented behavior permits it. Archal states it does not claim complete upstream coverage without measured, dated evidence.

Can one sandbox contain multiple environments?

Yes. You choose every environment your workflow needs when you create the sandbox. Each environment receives its own endpoint and readiness state. Each environment costs $0.10 per minute.

Does traffic ever reach the real provider?

Environment traffic is routed to Archal-managed implementations, not your production accounts. Each environment profile documents any exceptional dependency or behavior before use.

How does billing work?

Self-serve usage has no subscription and requires no card to start. New accounts receive $5 after verified signup and another $15 when their first sandbox is ready. Each environment costs $0.10 per minute. Billing is prorated by the second; failed provisioning and cold-start time are free. Paid continuation is not yet available while its safety rollout remains disabled.

Similar tools

Explore category