Validate Citation Format

legal.citation_format_validate

ProductionBounded custom (Class B)Deterministicstrictfastv1.0.0

No network

Overview

You send citations and one profile: ECLI, CELEX, DOI or GENERIC_CASE_BASIC. We apply the published citation-format-v1 grammar and return parsed components or syntax diagnostics. A match is not evidence the authority exists or remains good law. A successful call costs 1 execution credit.

Identifier syntax can be checked mechanically; treating a match as good law would be research.

Reliability

CITATION_LIMIT_EXCEEDED — trigger: more than 10000 citations; retryable: no; next: split the list.

Context footprint

Identifier strings only. A successful call costs 1 execution credit.

When to use it

When you already have an identifier and need to know whether it matches ECLI, CELEX, DOI or the basic generic case form.

When you need Bluebook completeness, a shepardising-style check, or footnote formatting.

Scope

Note

Validates citation identifiers against the published citation-format-v1 grammars.

Non-goals

Does not implement Bluebook or OSCOLA completeness
Does not check that a cited authority exists
Does not format footnotes

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

parsingvalidation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input2 MB

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
citations	array	Yes	Citation strings, 1 through 10001 entries; runtime accepts at most 10000.
profile	string	Yes	ECLI, CELEX, DOI or GENERIC_CASE_BASIC.
expectedJurisdiction	string	No	Jurisdiction token for GENERIC_CASE_BASIC only; omit it when that check is not wanted.

Output schema

Field	Type	Required	Description
valid	boolean	Yes	True when every citation matched the selected grammar.
profile	string	Yes	Grammar that was applied.
grammarVersion	string	Yes	Published grammar identifier.
results	array	Yes	Per-citation rows in request order, 1 through 10000 entries.
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.citation_format_validate","input":{"citations":["ECLI:NL:HR:2013:BY8111"],"profile":"ECLI"}}'

Integrations

TypeScript SDK

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

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

const { output } = await sq.execute("legal.citation_format_validate", {"citations":["ECLI:NL:HR:2013:BY8111"],"profile":"ECLI"});

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.
CITATION_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 implement Bluebook or OSCOLA completeness
Does not check that a cited authority exists
Does not format footnotes
Legal research
Footnote restyling

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "legal.citation_format_validate",
  "input": {
    "citations": [
      "ECLI:NL:HR:2013:BY8111"
    ],
    "profile": "ECLI"
  }
}

Examples

A published Dutch Supreme Court ECLI matches

Inputjson

{
  "citations": [
    "ECLI:NL:HR:2013:BY8111"
  ],
  "profile": "ECLI"
}

Expected outputjson

{
  "results": [
    {
      "citation": "ECLI:NL:HR:2013:BY8111",
      "valid": true,
      "components": {
        "country": "NL",
        "court": "HR",
        "year": "2013",
        "ordinal": "BY8111"
      },
      "diagnostics": []
    }
  ],
  "profile": "ECLI",
  "valid": true,
  "grammarVersion": "citation-format-v1",
  "assumptions": [
    "Only the ECLI grammar in citation-format-v1 is applied.",
    "A matching identifier is not evidence that the cited authority exists or remains good law."
  ],
  "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."
}

Tip

The five ECLI parts parse; existence of the case is not checked.

A DOI with a 10. prefix and suffix matches