# ONE Engine Blob Decoder

> ONE Engine Blob Decoder is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0069/call, status unknown (last checked 2026-10-02).

Identifies and decodes opaque or encoded text blobs (e.g. base64) into their plaintext representation with step-by-step decoding metadata.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/decode/blob?utm_source=zero.xyz
- Price: $0.0069/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-blob-decoder-1069adc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oHF8Z6oyedhS2UtIOT75i

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 one-engine-blob-decoder-1069adc0 -d '<json body>'
```

Example prompt: Can you decode this blob for me — I think it might be base64 but I'm not sure: 'SGVsbG8gd29ybGQ='?

## When to prefer this

Use this endpoint when an agent encounters an opaque or encoded string of unknown format and needs to identify its encoding and convert it to readable plaintext in a single step, especially in low-cost pay-per-call autonomous agent workflows on Base using x402 micropayments.

## Known failure modes

- Unrecognized encoding format returns an error or null result
- Malformed or truncated input may cause decoding failure
- Non-encoded plain text passed as input may return unchanged or misidentified
- Empty value field results in a validation error

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

Returns a JSON object containing the decoding steps applied (e.g. ['base64_decode']), the decoded plaintext result, a product label ('decode_blob'), and what the input was identified as (e.g. 'encoded_text').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "string",
   "description": "Opaque or encoded text to identify and decode"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "steps": [
   "base64_decode"
  ],
  "result": "Hello world",
  "product": "decode_blob",
  "identified_as": "encoded_text"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-blob-decoder-1069adc0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)