Get a TinyAgent Run as Structured JSON

Capability: output_schema

Use this when you need the result to land in a fixed shape every time — one field is enough for a schema, not for assembling a whole dataset.

Run It With a Schema

Type your goal

Write the goal as usual. Next to it, the Schema button is where you’ll define the shape of the result.

Agent Playground with the goal typed and a tooltip on the Schema button explaining structured output

Click Schema to define the result shape instead of free text.

Define the output schema

Build the shape field by field. Here, products is an array of objects, each with a name (string) and price (string — this page’s prices include a currency symbol, so a number field would silently drop them; see Common Mistakes below).

Output Schema builder with a products array field containing name and price fields

Add each field and its type, then click Save.

Run it

The goal box now shows Schema: On. Click Run.

Agent Playground with Schema On badge next to the Run button

Schema: On confirms it’s attached — then click Run.

Watch it run live

Live run view showing the ScrapeMe shop page being visited

The agent visits the page and extracts the data while you watch.

Read the structured result

The result matches the schema exactly — same field names, same types, every time.

Completed run result shown as JSON matching the defined schema exactly

Raw JSON, shaped exactly like the schema.

Toggle to a table for the same data:

Same result toggled to a readable table view

Same result, table view.

Or With the API

from tinyfish import TinyFish

client = TinyFish()

run = client.agent.run(
    url="https://scrapeme.live/shop",
    goal="Extract the first 2 product names and prices.",
    output_schema={
        "type": "object",
        "properties": {
            "products": {
                "type": "array",
                "items": {
                    "type": "object",
                    "properties": {
                        "name": {"type": "string"},
                        "price": {"type": "string"},
                    },
                    "required": ["name", "price"],
                },
            },
        },
        "required": ["products"],
    },
)

print(run.result)

import { TinyFish } from "@tiny-fish/sdk";

const client = new TinyFish();

const run = await client.agent.run({
  url: "https://scrapeme.live/shop",
  goal: "Extract the first 2 product names and prices.",
  output_schema: {
    type: "object",
    properties: {
      products: {
        type: "array",
        items: {
          type: "object",
          properties: {
            name: { type: "string" },
            price: { type: "string" },
          },
          required: ["name", "price"],
        },
      },
    },
    required: ["products"],
  },
});

console.log(run.result);

curl -X POST https://agent.tinyfish.ai/v1/automation/run \
  -H "X-API-Key: $TINYFISH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://scrapeme.live/shop",
    "goal": "Extract the first 2 product names and prices.",
    "output_schema": {
      "type": "object",
      "properties": {
        "products": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": { "type": "string" },
              "price": { "type": "string" }
            },
            "required": ["name", "price"]
          }
        }
      },
      "required": ["products"]
    }
  }'

Result

{
  "products": [
    { "name": "Bulbasaur", "price": "£63.00" },
    { "name": "Ivysaur", "price": "£87.00" }
  ]
}

The schema wins over the wording of the goal — if the schema describes a single object, you get a single object even if the goal says “list all of them.” So list results always need an array field (see Returning a List of Items).

Common Mistakes

A field silently drops instead of erroring

If a field’s type can’t hold what the page actually shows, the agent drops that item from the result instead of failing loudly. The price on this page renders as £63.00 — a number field can’t hold the currency symbol, so a price: { "type": "number" } schema returns "products": [] instead of an error. Use "type": "string" when the source text isn’t a bare number, as this guide now does.

Schema built but not turned on

Building fields in the Schema panel and clicking Save does not enable enforcement by itself — the separate Output Schema toggle at the top of the panel must also be switched to On. The goal box shows Schema: On only once both steps are done; if you only did the first, the schema is silently ignored.

Structured Output Reference

Supported types, keyword allowlist, size/depth limits, common rewrites

TinyAgent Reference

Full request and response schema

Start Here

Search API

Monitor

Fetch API

Browser API

Research API

Datasets API

Capabilities

Tools & Integrations

Guides

Use Cases

Reference

Get a TinyAgent Run as Structured JSON

Run It With a Schema

Or With the API

Common Mistakes

Structured Output Reference

TinyAgent Reference

​Run It With a Schema

​Or With the API

​Common Mistakes

​Related

Structured Output Reference

TinyAgent Reference

Run It With a Schema

Or With the API

Common Mistakes

Related