Skip to main content
Tool outputs are plain strings keyed by name, so piping one into another needs no glue beyond reading the right field.

Decode, then format

Take a base64-encoded JSON payload and produce something readable:
Two calls, two charges — each one billed at your plan’s minimum, since neither tool carries a weight above it.
Each hop costs credits and a round trip. Many tools already do the composite job in one call — GET /v1/tools/search is free, so check before building a pipeline.

Validate before you spend

For expensive tools, run a cheap validator first rather than paying for a failure you could have predicted:
Failed calls are refunded, so this is about your error handling rather than saving credits.

Batching

There is no batch endpoint. Call the tool once per item, respecting the rate limit:
Watch credits_remaining on each response — it is the cheapest possible progress meter.