# Vietls Developer Pricing and Access

[Developers](https://www.vietls.com/developers)

Controlled beta

## Current status

Approved beta tokens allow no-spend quotes and test jobs. Artifacts are empty and no checkout URL is created. API keys and actual paid execution remain restricted; purchasing a plan does not automatically approve developer access.

- [Pricing](https://www.vietls.com/pricing)

## Commerce boundary

An agent may validate a paid plan selection after user confirmation through hosted checkout handoff via `POST /api/public/v1/checkout/handoffs`. The test response returns `checkoutUrl: null` and never creates a provider checkout session.

Live checkout URLs may be enabled only after return-URL allowlisting and first-purchase checks pass. Users complete payment in the provider’s hosted checkout; agents must not collect or enter card details.

## Policies

- [Billing and Credit Policy](https://www.vietls.com/pricing/billing-and-credit-policy)

- [Refund Policy](https://www.vietls.com/pricing/refund-policy)

- [Subscription Service Terms](https://www.vietls.com/pricing/subscription-service-terms)

## Paid workflow rule

API and MCP workflows with provider costs must quote, reserve, execute, then commit or release. A confirmed failure, cancellation, malformed result, or unusable output may release reserved credits under the workflow policy. Closing a tab or losing a response is not confirmation of provider failure or cancellation; an unresolved operation must be reconciled before releasing its reservation.

Use `POST /api/public/v1/billing/simulations` to test reservation, commitment, and release without changing the ledger or spending credits.

In dry-run mode, `POST /api/public/v1/checkout/handoffs` creates no subscription, no charge, and no provider checkout URL.