# agentbit.app Text-to-JSON Extractor

> agentbit.app Text-to-JSON Extractor is a paid API for AI agents from agentbit.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Converts unstructured text into a validated JSON object using a provided schema or plain-English extraction instructions.

## Facts

- Endpoint: POST https://agentbit.app/v1/ai/extract?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentbit-app-text-to-json-extractor-f4f70b60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZSTn2-8deV8LZoAUYLVnx

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-app-text-to-json-extractor-f4f70b60 -d '<json body>'
```

Example prompt: Take this raw customer email and extract the sender's name, order number, and complaint topic as a clean JSON object — use the schema: {name: 'customer full name', order_number: 'order ID mentioned', complaint: 'main issue described'}.

## When to prefer this

Choose this endpoint when you have unstructured or semi-structured text and need a validated, schema-conforming JSON object back without writing custom parsing logic. It is particularly useful when the structure is defined at runtime (e.g. user-supplied schemas) or when plain-English instructions are more practical than formal schemas. Prefer this over general LLM calls when you need guaranteed JSON output with field-level extraction rather than a free-form narrative response.

## Known failure modes

- Input text exceeds ~16 KB limit — request may be truncated or rejected
- No schema or instructions provided — extraction may be ambiguous or fail
- Requested fields not present in source text — missing fields returned as null or omitted
- Malformed schema object — may cause validation errors or incorrect extraction
- Text is too ambiguous for reliable extraction — low-confidence values may be returned

## How this service works

Turn messy text into clean JSON. Pass text plus a field `schema` or plain `instructions`; get a validated JSON object back. Uses the provider JSON mode.

## Output

A validated JSON object with the fields specified in the schema or derived from the plain-English instructions, populated with values extracted from the input text. The response conforms to JSON mode output, ensuring it is always parseable and structurally valid.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "Source text to extract from (required, up to ~16 KB)."
  },
  "schema": {
   "type": "object",
   "description": "Optional map of field name → description of the value to extract."
  },
  "instructions": {
   "type": "string",
   "description": "Optional plain-English extraction instructions (used if no schema)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentbit-app-text-to-json-extractor-f4f70b60/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)