Validate Signature Block

legal.signature_block_validate

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0

No network

Overview

You send the expected parties and the blocks you already extracted. We check coverage, duplicate party blocks, blank names and the SIGNATURE, DATE, TITLE or WITNESS flags you listed. signaturePresent is only a boolean. A successful call costs 1 execution credit.

Signature-page checklists are completeness mechanics; treating a boolean as a verified signature would be advice.

Reliability

SIGNATURE_LIMIT_EXCEEDED — trigger: more than 64 parties, 64 blocks or 8 witnesses; retryable: no; next: trim the lists.

Context footprint

Names and booleans only; no image bytes. A successful call costs 1 execution credit.

When to use it

When blocks are already extracted and you need party coverage plus your own required flags.

When you need to authenticate ink, a certificate or signatory authority.

Scope

Note

Checks extracted signature blocks for party coverage and caller-selected completeness flags.

Non-goals

Does not authenticate a signature or certificate
Does not recognise handwriting
Does not decide signatory authority

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

validation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input64 KB

How we handle your data

Sensitive input, safe output

What this means

This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response does not contain submitted content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
expectedParties	array	Yes	Expected parties with id and type, 1 through 65 entries; runtime accepts at most 64.
blocks	array	No	Extracted signature blocks, 0 through 65 entries; runtime accepts at most 64. Omit it for none.
required	array	No	SIGNATURE, DATE, TITLE or WITNESS flags applied to each block; omit it for coverage-only checking.

Output schema

Field	Type	Required	Description
valid	boolean	Yes	True when no ERROR diagnostic was produced.
coverage	array	Yes	Per-block coverage rows in request order, 0 through 64 entries.
diagnostics	array	Yes	Deterministically ordered diagnostics, 0 through 500 entries, each with code, severity, message and path; empty when nothing was flagged.
assumptions	array	Yes	Caller-visible mechanical assumptions for this answer, such as default weekend days or a grammar version, never a legal conclusion.
limitations	string	Yes	Fixed notice that only supplied parameters are applied and that validity, compliance and enforceability are not determined.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"legal.signature_block_validate","input":{"expectedParties":[{"id":"p-buyer","type":"ORGANIZATION"}],"blocks":[{"partyId":"p-buyer","signatoryName":"Alex Rivera","signaturePresent":true}]}}'

Integrations

TypeScript SDK

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

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

const { output } = await sq.execute("legal.signature_block_validate", {"blocks":[{"title":"Director","partyId":"p-buyer","witnesses":[{"name":"Sam Lee"}],"signatoryName":"Alex Rivera","capacity":"for Northwind Ltd","date":"2024-03-01","signaturePresent":true}],"required":["SIGNATURE","DATE","TITLE","WITNESS"],"expectedParties":[{"type":"ORGANIZATION","id":"p-buyer"}]});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
SIGNATURE_LIMIT_EXCEEDED	429	No	A size, quota, rate, or time limit was exceeded.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not authenticate a signature or certificate
Does not recognise handwriting
Does not decide signatory authority
e-signing
Handwriting recognition

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "legal.signature_block_validate",
  "input": {
    "blocks": [
      {
        "title": "Director",
        "partyId": "p-buyer",
        "witnesses": [
          {
            "name": "Sam Lee"
          }
        ],
        "signatoryName": "Alex Rivera",
        "capacity": "for Northwind Ltd",
        "date": "2024-03-01",
        "signaturePresent": true
      }
    ],
    "required": [
      "SIGNATURE",
      "DATE",
      "TITLE",
      "WITNESS"
    ],
    "expectedParties": [
      {
        "type": "ORGANIZATION",
        "id": "p-buyer"
      }
    ]
  }
}

Examples

Organization block with signature, date, title and witness

Inputjson

{
  "blocks": [
    {
      "title": "Director",
      "partyId": "p-buyer",
      "witnesses": [
        {
          "name": "Sam Lee"
        }
      ],
      "signatoryName": "Alex Rivera",
      "capacity": "for Northwind Ltd",
      "date": "2024-03-01",
      "signaturePresent": true
    }
  ],
  "required": [
    "SIGNATURE",
    "DATE",
    "TITLE",
    "WITNESS"
  ],
  "expectedParties": [
    {
      "type": "ORGANIZATION",
      "id": "p-buyer"
    }
  ]
}

Expected outputjson

{
  "limitations": "Calculations use only the parameters supplied in this call. No implicit legal rule is applied, and the answer does not determine validity, compliance or enforceability.",
  "coverage": [
    {
      "partyId": "p-buyer",
      "signaturePresent": true,
      "date": "2024-03-01",
      "witnessCount": 1
    }
  ],
  "valid": true,
  "assumptions": [
    "signaturePresent is a caller boolean; no signature image or certificate is inspected.",
    "Witness, date and title requirements apply only when listed in required."
  ],
  "diagnostics": []
}

Tip

All four required flags are present, so valid is true.

Second expected party has no block