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

# Test in sandbox

> Every test knob in one place. Sandbox looks exactly like production, so this page is where the knobs become visible.

There is one API, `api.agentcard.sh`. Sandbox is not a different URL; it's what you get when you authenticate with sandbox credentials. Everything behaves the same, except nothing is real: no emails, no SMS, no money.

The catch is that sandbox looks so much like production that its shortcuts are invisible. API responses never mention them. Here they all are.

## The knobs

| Knob                                      | What it does                                                                                                                                     |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| Code `111111`                             | The one-time code for everything: connecting users, phone verification. Sandbox never sends a real code, and this one always works.              |
| Card `4242 4242 4242 4242`                | Adds instantly in the wallet with any future expiry and any CVC.                                                                                 |
| Card `4242 4300 0000 0017`                | Runs the full real add ceremony against the test network, if you want to see every step.                                                         |
| `POST /api/v2/kyc/simulate`               | Sets a user's verification outcome: `approved`, `rejected`, or `requires_input`. Returns 403 outside sandbox.                                    |
| `agent-cards companies balance test-fund` | Adds sandbox balance so you can issue Agentcards and spend.                                                                                      |
| `test_charge`                             | On [MCP](/tools/mcp), connected as your organization: simulates a full charge against a card, with authorization, settlement, and every webhook. |

## Sandbox users are isolated

Any email or phone works in sandbox, including real ones, and it can never touch a real account. Sandbox identities live in their own namespace, so `ceo@yourcustomer.com` in sandbox is not, and can never become, that person's account.

## What has no sandbox

A few balance funding providers are production-only, so end-to-end onramp payments can't be simulated. Use `test-fund` for balance in sandbox and verify the real funding flow with a small amount when you go live.

## Simulate a full flow

This is the whole product in six sandbox steps, most of it covered by the [Quickstart](/get-started/quickstart):

1. Connect a user with `111111`.
2. Create a wallet link and open the wallet.
3. Add `4242 4242 4242 4242`, and watch `connected_card.updated` arrive.
4. Simulate KYC approval, `test-fund` some balance, and issue an Agentcard.
5. Run `test_charge` against it, and watch `transaction.authorized` and `transaction.cleared` arrive.
6. Check the deliveries log in the dashboard. That's every event your production endpoint will need to handle.

Next: [Go live](/ship/go-live)