How much does a pptx-to-text call cost?

$0.005 per call, paid in USDC on Base via x402, with no account and no API key.

What does pptx-to-text return?

A JSON object with 5 top-level fields: source_url, slide_count, chars, slides and text. The example on this page is a real call over documents/garden-plan.pptx.

What happens when a pptx-to-text call fails?

The tool answers with a typed JSON error from the errors table. Payment is settled only after the tool has produced its result; a call that fails inside the tool is never settled. A 503 upstream_unavailable can follow a settled call; the x402 payments guide covers it, 429, 402 and an uncertain 500.

catalogue / tools / Documents / PPTX to Text API

PPTX to Text API

Extracts the slide text of a PowerPoint .pptx, slide by slide, in order (body text only, up to 1,000 slides).

Endpoint: POST /v1/pptx-to-text
Price: $0.005 per call
Family: Documents
Docs: /docs/pptx-to-text

01When to use it

Reading .pptx slide text needs to unpack an OOXML zip through a hardened fetch: an agent fetching the URL itself walks past every SSRF control, and the parsing is fiddly enough to be worth a paid endpoint.
Your source is PPTX and you need plain text.

When not to use it

The input is over 25 MB (26,214,400 bytes): pptx-to-text answers too_large (413).
The destination needs more than 40 s to answer: the call ends with upstream_timeout (424).
The destination is on a private or local network: the network guard refuses it with blocked_target (403).

02Parameters

Field	Type	Required	Description
url	string	yes	Absolute http(s) URL of the .pptx, up to 2048 characters; redirects are followed and the body must be a zip holding ppt/slides/slideN.xml parts, at most 1,000 of them.

03Limits

Limit	Value
Largest source file	25 MB (26,214,400 bytes)
Timeout	40 s
Source formats	PPTX
Output formats	plain text

04Example

The published example of pptx-to-text, verbatim: the request body and the response it returns.

Request

POST /v1/pptx-to-text
content-type: application/json
payment-signature: <base64 x402 payload>

{
  "url": "https://grist.tools/samples/documents/garden-plan.pptx"
}

Response

200 OK
payment-response: <base64 settlement receipt>

{
  "source_url": "https://grist.tools/samples/documents/garden-plan.pptx",
  "slide_count": 3,
  "chars": 244,
  "slides": [
    {
      "number": 1,
      "text": "Spring Planting Plan\nCommunity garden season overview"
    },
    {
      "number": 2,
      "text": "Beds and Crops\nNorth beds: beans and peas\nSouth beds: tomatoes & peppers\nHerb spiral: basil, thyme, mint"
    },
    {
      "number": 3,
      "text": "Next Steps\nOrder compost by March\nRepair the east fence\nSchedule the first work day"
    }
  ],
  "text": "Spring Planting Plan\nCommunity garden season overview\n\nBeds and Crops\nNorth beds: beans and peas\nSouth beds: tomatoes & peppers\nHerb spiral: basil, thyme, mint\n\nNext Steps\nOrder compost by March\nRepair the east fence\nSchedule the first work day"
}

Sample file: documents/garden-plan.pptx. Three-slide PowerPoint deck (a garden planting plan): a title slide and two bullet slides, one line holding an escaped ampersand, hand-written PresentationML with pinned zip dates.

The returned text runs to 12 lines, 2 blank ones among them, and its longest line, "Community garden season overview", holds 32 characters. Its first line reads "Spring Planting Plan" and its last "Schedule the first work day". Split on whitespace, it yields 40 tokens over 10 non-blank lines.

Response field	Type	In the example
source_url	string	"https://grist.tools/samples/documents/garden-plan.pptx"
slide_count	number	3
chars	number	244
slides	array	3 items, each with number and text
text	string	"Spring Planting Plan Community garden season overview Beds and Crops North beds: beans and peas South beds: tomatoes & peppers Herb spiral: basil, thyme, mint Next Steps Order compost by March Repair the east fence Schedule the first work day"

05Call it from code

JavaScript

// pptx-to-text: $0.005 per call, paid in USD Coin on eip155:8453 via x402
// Install: npm install @x402/fetch@2 @x402/evm@2 viem@2
// Save as client.mjs (ES module, Node 18+), export EVM_PRIVATE_KEY with the paying wallet's key in your shell, then run: node client.mjs
// The wrapper reads the 402 (payment-required), signs and retries with payment-signature.
import { wrapFetchWithPayment, x402Client, decodePaymentResponseHeader } from '@x402/fetch'
import { ExactEvmScheme } from '@x402/evm/exact/client'
import { privateKeyToAccount } from 'viem/accounts'

const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY)
const client = new x402Client().register('eip155:8453', new ExactEvmScheme(account))
const fetchWithPayment = wrapFetchWithPayment(fetch, client)

const body = {
  "url": "https://grist.tools/samples/documents/garden-plan.pptx"
}

const res = await fetchWithPayment('https://grist.tools/v1/pptx-to-text', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify(body),
})
console.log(res.status, await res.json())
const settle = res.headers.get('payment-response')
if (settle) console.log(decodePaymentResponseHeader(settle).transaction)

Python

# pptx-to-text: $0.005 per call, paid in USD Coin on eip155:8453 via x402
# Install: pip install "x402[requests,evm]>=2.24,<3"
# The session reads the 402 (payment-required), signs and retries with payment-signature.
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http import decode_payment_response_header
from x402.http.clients.requests import x402_requests
from x402.mechanisms.evm.exact import register_exact_evm_client
from x402.mechanisms.evm.signers import EthAccountSigner

account = Account.from_key(os.environ["EVM_PRIVATE_KEY"])
client = x402ClientSync()
register_exact_evm_client(client, EthAccountSigner(account), networks="eip155:8453")
session = x402_requests(client)

payload = {
    "url": "https://grist.tools/samples/documents/garden-plan.pptx"
}

res = session.post("https://grist.tools/v1/pptx-to-text", json=payload)
print(res.status_code, res.json())
settle = res.headers.get("payment-response")
if settle:
    print(decode_payment_response_header(settle).transaction)

curl

# pptx-to-text: $0.005 per call, paid in USD Coin on eip155:8453 via x402
# 1. Unpaid call: HTTP 402, the requirements in the payment-required header (base64 JSON) and in the body.
curl -i -X POST 'https://grist.tools/v1/pptx-to-text' -H 'content-type: application/json' -d '{"url":"https://grist.tools/samples/documents/garden-plan.pptx"}'

# 2. Same call with the signed payment (an EIP-3009 authorization, EIP-712 signed: it cannot be
#    typed by hand). x-payment is accepted as the v1 alternative. HTTP 200 carries payment-response.
curl -i -X POST 'https://grist.tools/v1/pptx-to-text' -H 'content-type: application/json' -H 'payment-signature: <base64 x402 payload>' -d '{"url":"https://grist.tools/samples/documents/garden-plan.pptx"}'

06Errors

Code	HTTP	For this service
invalid_input	400	The body does not match the schema; its fields are url.
blocked_target	403
unreachable_target	424
upstream_timeout	424
unsupported_content_type	415	The source is not a type pptx-to-text reads; it reads PPTX.
too_large	413
unprocessable	422
internal	500

Input that is rejected before the tool runs (malformed JSON, schema mismatch, body over the size limit) is never charged.

When each code is raised, and what it means for payment: /docs/pptx-to-text.

07Conversions

Conversion	Recorded sample	Source size	Output size
PPTX to plain text	documents/garden-plan.pptx	6.8 KB	244 bytes

08Questions

How much does a pptx-to-text call cost?: $0.005 per call, paid in USDC on Base via x402, with no account and no API key.
What does pptx-to-text return?: A JSON object with 5 top-level fields: source_url, slide_count, chars, slides and text. The example on this page is a real call over documents/garden-plan.pptx.
What happens when a pptx-to-text call fails?: The tool answers with a typed JSON error from the errors table. Payment is settled only after the tool has produced its result; a call that fails inside the tool is never settled. A 503 upstream_unavailable can follow a settled call; the x402 payments guide covers it, 429, 402 and an uncertain 500.

09Related

Documents guide