ASCII85 Encoder API

GET

Pack data into more compact ASCII text than standard Base64.

ASCII85 Encoder encodes text into Base85 strings or decodes existing ASCII85 payloads back to plain text. Each request returns the converted output with original and processed character counts, while paid plans add custom formats and compression ratios.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/ascii85encoder?text=Hello%20World

Query parameters

textstring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "original_text": "Hello World",
    "encoded": "87cURD]i,\"Ebo7",
    "format": "standard",
    "original_length": 11,
    "encoded_length": 14,
    "compression_ratio": "127.27%"
  }
}

About the ASCII85 Encoder API

ASCII85 Encoder works by converting binary data to ASCII text using base-85 encoding, which represents 4 bytes with 5 ASCII characters. Includes special handling for zero bytes and format delimiters.

What people use it for

Data Encoding: Encode binary data for text-based transmission with better compression than Base64
PDF Processing: Handle ASCII85-encoded data in PDF files and PostScript documents
Data Serialization: Serialize binary data for storage in text-based formats like JSON or XML
Compression: Achieve better compression ratios for binary data in text-only protocols

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use ASCII85 Encoder

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the ASCII85 Encoder API.

Read the docs →

How many conversions does the Free plan cover?

The Free plan covers 100 conversions each month using its 200 included credits. If your volume grows, the Starter plan provides 100,000 conversions per month, which works out to about $0.30 per 1,000 calls.

Can I check the compression ratio on the Free plan?

No. The compression ratio and format fields are premium features unlocked on paid plans. Free tier requests return the original text, converted string, and character length measurements.

Does the encoder support the btoa Base85 variation?

Yes, on paid plans. ASCII85 Encoder supports both standard Base85 and the btoa format variant. You can encode plain strings into either standard or decode existing payloads back to their original form.

How does the encoder handle runs of zero bytes?

The service implements standard Base85 rules for zero-byte runs and delimiter characters. It maps every four bytes of source data into five printable ASCII characters while handling zero-value sequences cleanly.

Are custom format parameters permitted on the Free plan?

Specifying a custom format parameter is restricted to paid subscriptions. On the Free plan, requests run using default formatting, and the format field is omitted from the JSON response.

Request parameters — GET /v1/ascii85encoder

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`text`Required	string	`Hello World`	Text to encode

Optional

Parameter	Type	Example	Description
`action`Optional	string	`encode`	Action to perform `encodedecode` default encode
`format`OptionalPremium	string	`standard`	Output format `standardbtoa` default standard

Example request

1
2

curl "https://api.apiverve.com/v1/ascii85encoder?text=Hello%20World&action=encode&format=standard" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/ascii85encoder

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "original_text": "Hello World",
    "encoded": "87cURD]i,\"Ebo7",
    "format": "standard",
    "original_length": 11,
    "encoded_length": 14,
    "compression_ratio": "127.27%"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`original_text`	string	`"Hello World"`	The original input text before encoding
`encoded`	string	`"87cURD]i,"Ebo7"`	The encoded text in ASCII85 format
`format`Premium	string	`"standard"`	The encoding format used for conversion
`original_length`	number	`11`	The character count of the original text
`encoded_length`	number	`14`	The character count of the encoded text
`compression_ratio`Premium	string	`"127.27%"`	The size ratio of encoded to original text

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	ASCII85 Encoder calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/ascii85encoder

No SDK to install — this is a plain HTTPS call to /v1/ascii85encoder with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/ascii85encoder" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/ascii85encoder-apiSource, issues and the examples this page is built from.ReferenceASCII85 Encoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/ascii85encodernpm apiverve-ascii85encoderPyPI APIVerve.API.ASCII85EncoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/ascii85encoder

Install the Node.js SDK, then call the ASCII85 Encoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/ascii85encoder

Node.js

const res = await fetch("https://api.apiverve.com/v1/ascii85encoder", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/ascii85encoderThe published Node.js client, versioned and signed.GitHubapiverve/ascii85encoder-apiSource, issues and the examples this page is built from.ReferenceASCII85 Encoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-ascii85encoderPyPI APIVerve.API.ASCII85EncoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/ascii85encoder

Install the Python SDK, then call the ASCII85 Encoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-ascii85encoder

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/ascii85encoder",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-ascii85encoderThe published Python client, versioned and signed.GitHubapiverve/ascii85encoder-apiSource, issues and the examples this page is built from.ReferenceASCII85 Encoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/ascii85encodernpm APIVerve.API.ASCII85EncoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/ascii85encoder

Install the C# / .NET SDK, then call the ASCII85 Encoder API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.ASCII85Encoder

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/ascii85encoder");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.ASCII85EncoderThe published C# / .NET client, versioned and signed.GitHubapiverve/ascii85encoder-apiSource, issues and the examples this page is built from.ReferenceASCII85 Encoder API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/ascii85encodernpm apiverve-ascii85encoderPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/ascii85encoder

No SDK to install — this is a plain HTTPS call to /v1/ascii85encoder with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/ascii85encoder", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/ascii85encodernpm apiverve-ascii85encoderPyPI APIVerve.API.ASCII85EncoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/ascii85encoder

No SDK to install — this is a plain HTTPS call to /v1/ascii85encoder with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/ascii85encoder");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/ascii85encodernpm apiverve-ascii85encoderPyPI APIVerve.API.ASCII85EncoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/ascii85encoder

No SDK to install — this is a plain HTTPS call to /v1/ascii85encoder with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/ascii85encoder")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/ascii85encodernpm apiverve-ascii85encoderPyPI APIVerve.API.ASCII85EncoderNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Data Conversion

View all 33 →

All articles →

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Generate PDFs from HTML with an APIConvert HTML to PDF programmatically. Tutorial covering invoices, reports, receipts, and certificates with code examples.Read

Automating Visual Testing With ScreenshotsCatch visual bugs before users do. Here's how to add screenshot-based testing to your workflow.Read

ASCII85 Encoder API

Try it — live request, no key required

About the ASCII85 Encoder API

What people use it for

Ways to call it

Other ways to use ASCII85 Encoder

Questions.

Request parameters — GET /v1/ascii85encoder

Required

Optional

Authentication

Response — GET /v1/ascii85encoder

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/ascii85encoder

Resources

Also published for

Call it from Node.js — GET /v1/ascii85encoder

Resources

Also published for

Call it from Python — GET /v1/ascii85encoder

Resources

Also published for

Call it from C# / .NET — GET /v1/ascii85encoder

Resources

Also published for

Call it from Go — GET /v1/ascii85encoder

Resources

Also published for

Call it from PHP — GET /v1/ascii85encoder

Resources

Also published for

Call it from Ruby — GET /v1/ascii85encoder

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — ASCII85 Encoder API

Data Conversion

Related articles

Ready to build with ASCII85 Encoder? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog