# Agent Payload Tools – Pipeline

> Agent Payload Tools – Pipeline is a paid API for AI agents from api.agent-payload-tools.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Applies an ordered sequence of deterministic encoding, hashing, and JSON transformation operations to an input value in a single API call.

## Facts

- Endpoint: POST https://api.agent-payload-tools.workers.dev/pipeline
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-payload-tools-pipeline-ab5affd0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ecGMhnqQUdz6VrmTaFpRb

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-payload-tools-pipeline-ab5affd0 -d '<json body>'
```

Example prompt: Take the string 'hello world', first SHA256 hash it, then base64 encode the result — apply those two operations in order using the pipeline.

## When to prefer this

Choose this endpoint when you need deterministic, server-side encoding, hashing, or JSON transformation without running code locally — especially when chaining multiple operations (e.g. canonicalize → SHA256 → base64) in a single call. It is ideal for AI agents that cannot execute arbitrary code but need cryptographic or encoding primitives. Prefer it over general-purpose code execution tools when only encoding/hashing/JSON operations are needed, as it is cheaper and auditable.

## Known failure modes

- Invalid operation type specified — returns error if enum value is not one of the ten supported operations
- Input incompatible with operation — e.g. base64_decode on a non-base64 string returns a decoding error
- Chained operation type mismatch — e.g. trying to json_parse a value that is not a valid JSON string
- Exceeding maxItems of 12 operations returns a validation error
- Malformed input JSON in the request body returns 400
- Payment not included or invalid x402 payment header returns 402 status

## How this service works

Run 1 to 12 deterministic encoding, decoding, JSON, or hashing operations in sequence.

## Output

Returns the final transformed value after all ordered operations have been applied in sequence. The result type depends on the final operation — it may be a string (encoded/decoded), a hex digest, a base64 string, a parsed JSON object, or a canonical JSON string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "description": "Initial JSON-compatible value."
  },
  "operations": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "type"
    ],
    "properties": {
     "type": {
      "enum": [
       "base64_encode",
       "base64_decode",
       "hex_encode",
       "hex_decode",
       "url_encode",
       "url_decode",
       "json_parse",
       "json_canonicalize",
       "sha256",
       "sha512"
      ],
      "type": "string",
      "description": "Deterministic operation to apply to the current value."
     }
    }
   },
   "maxItems": 12,
   "minItems": 1,
   "description": "Ordered deterministic transformations."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-payload-tools-pipeline-ab5affd0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agent-payload-tools.workers.dev](https://www.zero.xyz/host/api.agent-payload-tools.workers.dev/llms.txt)