# AUTOGROK Desk — JSON Shape

> AUTOGROK Desk — JSON Shape is a paid API for AI agents from desk.grokaiapps.com, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-11).

Reshapes raw text or JSON into a structured JSON object matching a user-specified field schema hint, paying per call via USDC or prepaid card.

## Facts

- Endpoint: POST https://desk.grokaiapps.com/v1/jobs/json-shape?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/autogrok-desk-json-shape-7441303c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dXTxO5dEs1ZoUX1AOdkxQ

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 autogrok-desk-json-shape-7441303c -d '<json body>'
```

Example prompt: Take this raw text — 'name: Ada, age: 36, city: London' — and reshape it into a JSON object with fields name, age, and city.

## When to prefer this

Choose this endpoint when you need to convert raw or semi-structured text into a specific JSON shape and can describe the desired fields in plain language. It is ideal for normalizing scraped text, LLM outputs, or legacy data into a typed record without writing custom parsing code. Prefer it over generic LLM prompting when you want a reliable, paid micro-job with structured output guarantees and per-call cost accountability.

## Known failure modes

- Input text exceeds 50,000 character limit — request rejected
- Schema hint fields cannot be found in input text — data object returned with null or missing values
- Malformed input that is neither parseable text nor valid JSON — partial or empty data object returned
- Payment failure via x402 or prepaid card — 402 Payment Required response
- Ambiguous field names in schema hint causing incorrect key mapping

## How this service works

Paid micro-jobs for AI agents and people: URL probe, page extract, watch once, JSON shape, researched brief. Pay per call with x402 (USDC on Base) or with prepaid card packs (Stripe MPP).

## Output

Returns a JSON object with an 'ok' boolean, a 'data' object containing the reshaped fields populated from the input text, a 'notes' array explaining how parsing was performed and how many schema hint keys were matched, and the original 'schema_hint' echoed back.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "maxLength": 50000,
   "description": "Raw text or JSON to reshape (≤50k chars)"
  },
  "schema_hint": {
   "type": "string",
   "description": "Free-text hint of desired field names / shape"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {
   "age": 36,
   "name": "Ada"
  },
  "notes": [
   "parsed key:value lines",
   "schema_hint matched 2/2 keys"
  ],
  "schema_hint": "name, age"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/autogrok-desk-json-shape-7441303c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from desk.grokaiapps.com](https://www.zero.xyz/host/desk.grokaiapps.com/llms.txt)