[Integrations](https://spiral.ai/integrations) › [dots](https://spiral.ai/integrations/dots) › [Schematron V2 Turbo](https://spiral.ai/integrations/dots/schematron-v2-turbo)

# How to Use Schematron V2 Turbo in dots

Schematron V2 Turbo turns HTML into JSON for high-volume extraction tasks. It prioritizes throughput, while Schematron V2 Small prioritizes extraction quality on complex schemas and long pages.

|  |  |
| --- | --- |
| Model | Schematron V2 Turbo |
| Available through | OpenRouter |
| Category | LLM |
| Price | Up to $0.000801 per run at the default inputs. $0.039 per 1M input tokens, $0.195 per 1M output tokens. |
| Returns | text, json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with Schematron V2 Turbo in dots

- Each morning, fetch the product pages on my watchlist and use Schematron V2 Turbo to extract names and displayed availability. Use the same extraction schema with temperature zero, then report changes since the previous run.
- Every weekday, fetch the career pages on my watchlist and use Schematron V2 Turbo to extract job titles, employers, locations, and application links. Define the fields in the extraction schema and report newly listed roles.
- Each Monday, fetch the event pages I follow and use Schematron V2 Turbo to extract titles, displayed dates, venues, and registration links. Preserve the source date text and flag changed records.
- Every morning, fetch the publications on my reading list and use Schematron V2 Turbo to extract article headlines, bylines, dates, and links. Split large collections so each extraction response stays below 8,192 tokens.
- Once a week, fetch the company pages on my watchlist and use Schematron V2 Turbo to extract names, locations, and descriptions. Define the requested description in the schema and report changes from the previous run.

## How to set up Schematron V2 Turbo in dots

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send dots this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create an API key**: In the console, open API keys and create a key for your dot. Copy it.

2. **Send your dot this message**: Your dot reads Spiral's skill and asks for your API key.

```text
set up https://spiral.ai/SKILL.md
```

3. **Give your dot the key**: When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run Schematron V2 Turbo**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "openrouter",
    "model": "inference-net/schematron-v2-turbo",
    "input": {
      "messages": [
        {
          "role": "system"
        }
      ]
    }
  }'
```

Then paste one of the prompts above: dots finds Schematron V2 Turbo on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/dots

## Schematron V2 Turbo tools and prices

- [Inference.net: Schematron V2 Turbo](https://spiral.ai/tools/openrouter/inference-net/schematron-v2-turbo) (OpenRouter): Up to $0.000801 per run at the default inputs. $0.039 per 1M input tokens, $0.195 per 1M output tokens.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| seed |  | — |  |
| stop |  | — |  |
| min_p | 0 to 1 | — |  |
| top_k | 0 to … | — |  |
| top_p | 0 to 1 | — |  |
| max_tokens | 1 to 8192 | — | The most output tokens to generate. |

## What can you do with Schematron V2 Turbo in dots?

Keep structured records current as monitored pages change. Let the scheduled agent fetch fresh HTML, run schema-guided extraction, and compare the results with its previous run.

### Product catalog ingestion

Use Schematron V2 Turbo to extract product names, specifications, and category labels from product-page HTML into a consistent JSON structure.

### Competitor availability monitoring

Extract product names and displayed availability from freshly fetched HTML. Compare the resulting records between runs to identify changes.

### Company directory records

Turn company-page HTML into records containing organization names, website links, locations, and descriptions. Define each requested detail in the schema.

### Research evidence extraction

Extract selected facts and supporting passages from retrieved HTML before another model writes an answer. Keep the source URL with each record.

### Job listing aggregation

Extract job titles, employers, locations, and application links from listing HTML. Process large collections in smaller chunks to keep responses within the output limit.

### Event calendar ingestion

Convert event-page HTML into structured titles, displayed dates, venues, and registration links. Preserve the original date text for review.

### Article metadata collection

Extract headlines, bylines, publication dates, and article links from HTML for a searchable content index.

## Overview

- [OpenRouter](https://spiral.ai/providers/openrouter)
- [All dots guides](https://spiral.ai/integrations/dots)

## Schematron V2 Turbo in other agents

- [Amp](https://spiral.ai/integrations/amp/schematron-v2-turbo)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/schematron-v2-turbo)
- [Claude](https://spiral.ai/integrations/claude-desktop/schematron-v2-turbo)
- [Claude Code](https://spiral.ai/integrations/claude-code/schematron-v2-turbo)
- [Cline](https://spiral.ai/integrations/cline/schematron-v2-turbo)
- [Codex](https://spiral.ai/integrations/codex/schematron-v2-turbo)
- [Cursor](https://spiral.ai/integrations/cursor/schematron-v2-turbo)
- [Devin](https://spiral.ai/integrations/devin/schematron-v2-turbo)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/schematron-v2-turbo)
- [Gemini](https://spiral.ai/integrations/gemini/schematron-v2-turbo)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/schematron-v2-turbo)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/schematron-v2-turbo)
- [goose](https://spiral.ai/integrations/goose/schematron-v2-turbo)
- [Grok](https://spiral.ai/integrations/grok/schematron-v2-turbo)
- [Grok Build](https://spiral.ai/integrations/grok-build/schematron-v2-turbo)
- [Hermes](https://spiral.ai/integrations/hermes/schematron-v2-turbo)
- [Instinct](https://spiral.ai/integrations/instinct/schematron-v2-turbo)
- [Manus](https://spiral.ai/integrations/manus/schematron-v2-turbo)
- [Muse](https://spiral.ai/integrations/muse/schematron-v2-turbo)
- [Muse Code](https://spiral.ai/integrations/muse-code/schematron-v2-turbo)
- [n8n](https://spiral.ai/integrations/n8n/schematron-v2-turbo)
- [Notion](https://spiral.ai/integrations/notion/schematron-v2-turbo)
- [OpenClaw](https://spiral.ai/integrations/openclaw/schematron-v2-turbo)
- [opencode](https://spiral.ai/integrations/opencode/schematron-v2-turbo)
- [Perplexity](https://spiral.ai/integrations/perplexity/schematron-v2-turbo)
- [Raycast](https://spiral.ai/integrations/raycast/schematron-v2-turbo)
- [VS Code](https://spiral.ai/integrations/vscode/schematron-v2-turbo)
- [Windsurf](https://spiral.ai/integrations/windsurf/schematron-v2-turbo)
- [Zapier](https://spiral.ai/integrations/zapier/schematron-v2-turbo)

## More dots guides

- [Schematron V2 Small](https://spiral.ai/integrations/dots/schematron-v2-small)
- [Seed 2.0 Lite](https://spiral.ai/integrations/dots/seed-2-0-lite)
- [Sakana Namazu](https://spiral.ai/integrations/dots/sakana-namazu)
- [Seed 2.0 Mini](https://spiral.ai/integrations/dots/seed-2-0-mini)
- [Ripple 65B Preview](https://spiral.ai/integrations/dots/ripple-65b-preview)
- [Seed 2.1 Turbo](https://spiral.ai/integrations/dots/seed-2-1-turbo)

## Questions about Schematron V2 Turbo in dots

**Can dots use Schematron V2 Turbo?**

Yes. Add Spiral to dots as an MCP server, and dots can find and run Schematron V2 Turbo like any built-in tool.

**How much does Schematron V2 Turbo cost in dots?**

Up to $0.000801 per run at the default inputs. $0.039 per 1M input tokens, $0.195 per 1M output tokens. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.

**Do I need an OpenRouter account to use Schematron V2 Turbo in dots?**

You need no OpenRouter account. dots uses one Spiral API key for every tool, and Spiral runs Schematron V2 Turbo on its own OpenRouter account.

**How long does it take to set up Schematron V2 Turbo in dots?**

About two minutes: create an API key, then send your dot this message, then give your dot the key.

**Does dots wait while Schematron V2 Turbo runs?**

Schematron V2 Turbo runs in the background. dots starts the run, checks on it and gives you the text, json when it's ready.

**What is Schematron V2 best at?**

Turning messy HTML into JSON with a defined structure. It fits product ingestion, page monitoring, and extracting selected facts for research.

**How do I give Schematron V2 extraction instructions?**

Put the directions in the JSON schema and its field descriptions. Send the HTML as the content to extract from; ordinary conversational instructions do not control the extraction.

**How much HTML can Schematron V2 Turbo handle?**

Input and output share a 128K-token context window, and the response can contain up to 8,192 tokens. Split large pages or long result lists into smaller extractions.

**What temperature should I use?**

Use temperature 0. Inference.net says Schematron was trained to perform best at that setting.

**Should I clean the HTML first?**

Yes. Remove scripts, styles, and boilerplate while preserving the content you need; Inference.net recommends lxml to match the training preprocessing.

