DoAThing

POST /v1/core/base64-convert

Base64

Standard or URL-safe, and it handles binary correctly rather than mangling it through a string.

Encode or decode base64 now No key, no code — 1 credit either way.

curl -X POST "$DOATHING_API/v1/core/base64-convert" \
  -H "x-api-key: $DOATHING_KEY" \
  -H "content-type: application/json" \
  -d '{"text": "hello", "options": {"mode": "encode"}}'

Standard or URL-safe, and it handles binary correctly rather than mangling it through a string.

Encode or decode base64 and base64url, with optional padding control.

Input

Send either a text string or a file object. A file is decoded as UTF-8 and must be one of text/plain, text/markdown, text/html, text/csv.

Response

The result carries your remaining balance alongside it, so you can track spend without a second call.

{
  "text": "aGVsbG8=",
  "mode": "encode",
  "request_id": "37f01edb-0163-42a1-ac51-0acaef979800",
  "credits_remaining": 96
}

Cost

1 credit per call, whether it is run from the site or from the API — the credential differs, the price does not. A new account starts with 20 credits.

A rejected request still costs a credit: the authorizer decrements before the tool validates. A call rejected for a missing or invalid key is free.

Parameters

Generated from the endpoint’s own validation, so this is exactly what it accepts. A body field goes at the top level; an option goes inside options.

NameInTypeDefaultNotes
modeoptionsstring"encode"encode or decode. one of encode, decode
urlsafeoptionsbooleanfalseUse the URL-safe alphabet (`-` and `_`).
paddingoptionsbooleantrueKeep trailing `=` when encoding.