Extract JSON-LD

Overview

You send HTML you already have and we find every <script type="application/ld+json"> block in it, check each one parses as JSON, hand back the parsed content, and surface the @type it declares. No script ever runs and nothing is fetched, so a hostile page cannot make us do anything. This is extraction rather than schema.org review, which web.validate_json_ld covers. Accepts file input via file_ref — no need to extract file content first.

Fishing script blocks out with a regular expression breaks on real pages, and you want the content read without a browser anywhere near it.

When to use it

Scope

Non-goals

• Does not run any script on the page
• Does not fetch the page, or resolve the @context it points at
• Does not check schema.org rules, which web.validate_json_ld does
• Does not merge, reshape, or deduplicate the blocks it finds

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

File limits

Constraints this skill applies to your input and generated files. The “Limited by” column shows the static source of each cap; none of these can be raised by upgrading your plan.

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"web.extract_json_ld","input":{"html":"<script type=\"application/ld+json\">{}</script>"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("web.extract_json_ld", {"html":"<script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"Organization\",\"name\":\"Acme\"}</script>"});

Errors

Other limits

Limitations

• Does not run any script on the page
• Does not fetch the page, or resolve the @context it points at
• Does not check schema.org rules, which web.validate_json_ld does
• Does not merge, reshape, or deduplicate the blocks it finds
• Fetching the page — bring the markup with you
• Judging whether the structured data satisfies schema.org

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "web.extract_json_ld",
  "input": {
    "html": "<script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"Organization\",\"name\":\"Acme\"}</script>"
  }
}

Examples

{
  "html": "<script type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"Organization\",\"name\":\"Acme\"}</script>"
}

{
  "blocks": [
    {
      "index": 0,
      "validJson": true,
      "rawLength": 70,
      "type": "Organization",
      "json": {
        "name": "Acme",
        "@type": "Organization",
        "@context": "https://schema.org"
      }
    }
  ],
  "warnings": [],
  "blockCount": 1,
  "errors": []
}

{
  "validateJson": true,
  "html": "<script type=\"application/ld+json\">{not json}</script>"
}

{
  "blocks": [
    {
      "index": 0,
      "rawLength": 10,
      "validJson": false,
      "type": null
    }
  ],
  "warnings": [],
  "blockCount": 1,
  "errors": [
    "Block 0 is not valid JSON."
  ]
}

Recommended use cases

• Pull the structured data out of a page you have already saved
• Audit schema.org markup before you publish it
• Feed the blocks you find into web.validate_json_ld

Avoid for

• Fetching the page — bring the markup with you
• Judging whether the structured data satisfies schema.org

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags