---
title: "Paying Scriptivox as an agent"
description: "What is purchasable, the payment rails, and which of them are actually wired on this deployment."
canonical: "https://www.scriptivox.com/payments.md"
---

# Paying Scriptivox as an agent

> Two things are purchasable. One rail is wired here — a Stripe Checkout link
> that a human opens. This page says what the others are and why they are not.

## What you can buy

| | What it is | How it is billed |
|---|---|---|
| **Web plan** | Free, Pro or Team on the web app | Subscription. Includes unlimited transcription **done by a person in the browser** — it grants no API credit. |
| **API credit** | Prepaid balance for the transcription API | $0.20 per hour of audio, charged only on success. Failed and cancelled jobs cost nothing. |

Current prices: [https://www.scriptivox.com/pricing](https://www.scriptivox.com/pricing). They come from the plan catalog
and are not repeated here, so a cached copy of this page can never quote a stale number.

**If your goal is to transcribe files, you want API credit, not a web plan.** A web plan is
priced for one human at a keyboard; the API has no daily cap and bills what you use.

## Rails

| Rail | Status | What it is |
|---|---|---|
| **Stripe Checkout link** | LIVE | An agent starts checkout and receives a URL; the person opens it and pays by card. Works today for both web plans and API credit. |
| **Agentic Commerce Protocol** | PLANNED | A delegated card credential held by the agent platform, settled through Stripe. The route by which an agent buys a subscription with a real card rather than handing over a link. |
| **Agent Payments Protocol (AP2)** | PLANNED | Signed spend mandates authorising an agent to pay within limits its user set in advance. |

### Why the others are not usable yet

- **Agentic Commerce Protocol** — Stripe shared-payment-token support is provisioned by hand on this project and is not wired yet.
- **Agent Payments Protocol (AP2)** — No mandate verification key is configured.

## How to pay today

Only one rail is available here: **Stripe Checkout link**.

Over MCP, with a user token from the OAuth flow:

```
purchase_plan   { "plan": "monthly" }        -> a Stripe Checkout URL
top_up_balance  { "amount_cents": 2000 }     -> a Stripe Checkout URL
```

Neither charges anything on its own. You get a link; the person opens it and enters their
card. Hand the URL over and say what it is for — do not describe the purchase as complete.

## The 402 challenge

The API answers `402 Payment Required` when the balance cannot cover a job. There is no
`accepts` quote and no header you can pay with: this deployment has no rail an agent can
settle by itself. A 402 means "ask your human to top up".

Call `top_up_balance`, hand the person the Checkout URL, and wait. Do not retry the request
until `get_account` or `check_balance` shows the credit has landed — the balance moves when
Stripe confirms the payment, not when the link is opened.

## Related

- [https://www.scriptivox.com/auth.md](https://www.scriptivox.com/auth.md) — which credential to use
- [https://www.scriptivox.com/signup.md](https://www.scriptivox.com/signup.md) — creating the account first
- [https://www.scriptivox.com/pricing](https://www.scriptivox.com/pricing) — current prices
- [https://platform.scriptivox.com/docs/pricing](https://platform.scriptivox.com/docs/pricing) — API rates