# ZeroReader IBM Granite 4.0 Micro Chat Completion

> ZeroReader IBM Granite 4.0 Micro Chat Completion is a paid API for AI agents from api.zeroreader.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Runs fast, ultra-cheap chat completions using IBM Granite 4.0 Micro via a pay-per-call API

## Facts

- Endpoint: POST https://api.zeroreader.com/v1/ai/granite-micro?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zeroreader-ibm-granite-4-0-micro-chat-completion-48c1f103
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NsFQ6e2nqGmcb_M3Bflfa

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 zeroreader-ibm-granite-4-0-micro-chat-completion-48c1f103 -d '<json body>'
```

Example prompt: Send this conversation to IBM Granite 4.0 Micro and get a quick reply: system says 'You are a helpful assistant', user asks 'What is the capital of France?' — keep max tokens at 256 and temperature at 0.3.

## When to prefer this

Choose this endpoint when you need the cheapest possible chat completion call for simple, short tasks where a small model is sufficient — such as classification, keyword extraction, summarization of short text, or simple Q&A. Prefer it over larger sibling models (DeepSeek R1, GPT-OSS 120B) when cost and speed matter more than reasoning depth or long-context handling.

## Known failure modes

- Payment not received or invalid USDC payment — 402 response
- messages array missing required role or content fields — 400 validation error
- max_tokens exceeds 4096 limit — 400 error
- temperature out of 0–2 range — 400 error
- Model overloaded or unavailable — 503 or timeout
- Malformed JSON body — 400 parse error

## How this service works

IBM Granite 4.0 Micro — Ultra-cheap, fast responses. Best for simple tasks.

## Output

A chat.completion JSON object with an id, the generated assistant message content, and a finish_reason (e.g. 'stop'), mirroring the OpenAI chat completion response format.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "stream": {
   "type": "boolean",
   "default": false
  },
  "messages": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "role",
     "content"
    ],
    "properties": {
     "role": {
      "enum": [
       "system",
       "user",
       "assistant"
      ],
      "type": "string"
     },
     "content": {
      "type": "string"
     }
    }
   }
  },
  "max_tokens": {
   "type": "integer",
   "default": 1024,
   "maximum": 4096
  },
  "temperature": {
   "type": "number",
   "default": 0.7,
   "maximum": 2,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "id": "chatcmpl-example",
 "object": "chat.completion",
 "choices": [
  {
   "index": 0,
   "message": {
    "role": "assistant",
    "content": "I'm doing well!"
   },
   "finish_reason": "stop"
  }
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zeroreader-ibm-granite-4-0-micro-chat-completion-48c1f103/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zeroreader.com](https://www.zero.xyz/host/api.zeroreader.com/llms.txt)