Skip to content

Clone API · Live paused

Code generation will return.

Live code generation is paused. New live requests return 503 clone_generation_paused without charging credits or creating jobs. API keys and free test runs remain available.

Live paused · Free test runs · REST & MCP

POST /api/v1/clone-requests/test-runs
curl -X POST https://clonesite.ai/api/v1/clone-requests/test-runs \
-H "Authorization: Bearer cs_live_..." \
-H "Idempotency-Key: req_8273" \
-H "Content-Type: application/json" \
-d '{ "sourceUrl": "https://linear.app",
"prompt": "Clone as editable React." }'
202 Accepted
{
"id": "api_req_abc123",
"status": "queued",
"mode": "test",
"statusUrl": "/api/v1/clone-requests/api_req_abc123"
}

Integration testing

Keep your integration ready

01

Manage your key

Create or revoke API keys in /developers. No purchase is needed to test.

Authorization: Bearer cs_live_...
02

Check availability

Preflight reports canCreate=false, checks.generation=paused and wouldChargeCredits=0.

POST /api/v1/clone-requests/preflight
03

Run a free test

Exercise polling, signed webhooks and a fixture source ZIP without generating code.

POST /api/v1/clone-requests/test-runs

Test the lifecycle

Free mock requests progress to ready or failed. They do not create real generation jobs.

mode: test

No purchase needed

Test runs and fixture ZIP downloads cost zero credits. New live requests are blocked before charging.

0 credits

REST and MCP

Use the same bearer key for REST or hosted MCP. Both surfaces enforce the live pause.

clonesite.ai/openapi.json · /mcp

Preflight & test runs

Check the pause, test the flow

Preflight validates your payload and account settings while reporting the live pause. Free test runs exercise integration behavior with mock output.

  • canCreate=false · checks.generation=paused · wouldChargeCredits=0
  • Free test requests with optional signed webhooks
  • Polling and fixture source ZIP downloads remain available
POST /api/v1/clone-requests/preflight
curl -X POST https://clonesite.ai/api/v1/clone-requests/preflight \
-H "Authorization: Bearer cs_live_..." \
-H "Content-Type: application/json" \
-d '{ "sourceUrl": "https://linear.app", ... }'
200 OK · no charge
{
"canCreate": false,
"wouldChargeCredits": 0,
"checks": { "generation": "paused" }
}
free test run
curl -X POST https://clonesite.ai/api/v1/clone-requests/test-runs \
-H "Authorization: Bearer cs_live_..." \
-H "Idempotency-Key: test_8273" \
-H "Content-Type: application/json" \
-d '{ ..., "scenario": "ready" }'
# 202 · mode: test · 0 credits
# when ready: POST /source-downloads
# returns a fixture ZIP · 0 credits

Webhooks

Verify your test callbacks

Polling needs only an API key. To test callbacks, configure a signing secret in /developers and supply callbackUrl on a test run.

  • Account-level signing secret
  • Standard Webhooks HMAC-SHA256 signatures
  • Test ready and failed terminal events
POST your callback URL
webhook-id: evt_abc123
webhook-timestamp: 1781946000
webhook-signature: v1,base64(hmac_sha256(...))
{ "event": "clone.ready",
"cloneRequestId": "api_req_abc123",
"artifactSlug": "api-test-fixture",
"sourceZip": { "available": true, "creditCost": 0 }
}
verify
const sig = base64HmacSha256(secret, `${id}.${ts}.${body}`)
if (`v1,${sig}` !== header) return reject(401)

While generation is paused

Prepare your integration

API key management

Create and revoke credentials without buying credits.

Integration testing

Validate polling, webhook verification and fixture downloads.

Historical requests

Read existing status. Matching idempotent retries return the current request without new fulfillment.

Free integration tests

Live generation paused · No credits required for test runs

Manage API keys

FAQ

What remains available?

Can I create a live clone?

Live code generation is paused and will return. New live requests return HTTP 503 with code clone_generation_paused. No credits, API request records or jobs are created.

Can I keep testing?

Yes. Free test runs, polling, signed webhooks and fixture ZIP downloads remain available with an API key or OAuth access token.

What happens to retries?

The same idempotency key and payload return the existing request read-only. A different payload returns 409 idempotency_conflict. Existing queued or processing requests do not resume generation.

When will generation return?

There is no confirmed date. Follow the return announcement linked above; API key management and test mode remain available.

Keep your integration ready.

Manage API keys and test the flow for free while live generation is paused.

clonesite.ai/developers