# AgentBit Utility Transform

> AgentBit Utility Transform is a paid API for AI agents from agentbit.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Performs deterministic utility operations including SHA256/SHA512/HMAC hashing, JWT decode, base64 encode/decode, UUID generation, JSON validation, CSV↔JSON conversion, XML→JSON conversion, URL parsing, and semver comparison.

## Facts

- Endpoint: POST https://agentbit.app/v1/util/transform
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentbit-utility-transform-fac93de1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9ZOcQm9RloLFfoRVqQx-j

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 agentbit-utility-transform-fac93de1 -d '<json body>'
```

Example prompt: Can you SHA256-hash the string 'hello world' for me using the utility transform endpoint — I need the hex digest right now.

## When to prefer this

Choose this endpoint when you need fast, deterministic, stateless utility transformations — hashing, encoding, decoding, format conversion — without calling external services or storing data. Ideal for agent pipelines that need to preprocess or validate data inline at sub-millisecond latency. Prefer this over general-purpose code-execution endpoints when the specific operation (SHA256, base64, JWT decode, CSV→JSON, etc.) is already supported, and over cloud functions when you want a simple pay-per-call model with no infrastructure overhead.

## Known failure modes

- Invalid or unsupported operation name returns an error
- Missing required 'input' field causes a 400-level error
- Malformed base64 input causes decode failure
- Invalid JSON passed for JSON validation returns false or an error
- JWT with non-standard structure may fail to decode
- Unsupported algorithm value causes an error
- Missing 'key' field when HMAC operation is requested causes failure

## How this service works

Deterministic utility operations for agents: sha256/sha512/HMAC hashing, JWT decode, base64 encode/decode, UUID generation, JSON validation, CSV↔JSON, XML→JSON, URL parsing and semver comparison. Sub-millisecond, no external calls.

## Output

Returns the result of the requested utility operation as a structured JSON response — e.g. a hex hash digest for hashing operations, an encoded/decoded string for base64, a parsed JSON object for URL/CSV/XML/JWT operations, a boolean for validation, a UUID string, or a comparison result (-1, 0, 1) for semver. All processing is deterministic, sub-millisecond, and requires no external network calls.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "a": {
   "type": "string"
  },
  "b": {
   "type": "string"
  },
  "key": {
   "type": "string"
  },
  "input": {
   "type": "string"
  },
  "algorithm": {
   "type": "string"
  },
  "operation": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": "e03c51914240aba1419dac36a49c123150f78237c94212c1069634cdf69de715",
  "operation": "sha256"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentbit-utility-transform-fac93de1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentbit.app](https://www.zero.xyz/host/agentbit.app/llms.txt)