Rule-based clause tagging (obligation, prohibition, permission, condition, topic)

$0.005 USDC per call · Business, finance and compliance · POST /api/v1/clause-tag · Id clause-tag

Tags each contract-style clause you supply with the modal force it expresses (obligation, prohibition, permission, recommendation) and topic cues (definition, condition, termination, payment, confidentiality, liability, governing law, notice, assignment), with the matched cue and its offset. For an agent that must triage many clauses before a human or model reads them. Fixed cue phrases only (plus cues you add): a clause no rule decides is reported as undecided and the status is unknown. Not legal analysis, no model, and 'will' or a bare cue-less sentence is never forced into a tag.

What you get

Cheap deterministic first pass over up to 100 clauses; abstains instead of guessing.

Call it

Send the JSON body below to https://agents.writerslogic.com/api/v1/clause-tag. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.

curl -i -X POST https://agents.writerslogic.com/api/v1/clause-tag \
  -H 'content-type: application/json' \
  -d '{"clauses":["The Supplier shall deliver the Goods within 30 days of the Order.","Customer may not assign this Agreement without prior written consent.","This Agreement is governed by the laws of Ireland.","Thank you for your business."]}'

Input

Field	Type	Required	Description
`clauses`	array<string; length 0..3000>; max 100 items	yes	Up to 100000 characters in total.
`extraCues`	array<object>; max 100 items	no	Your own cue phrases, matched as literal word sequences.
`expect`	array<object>; max 100 items	no	Tags a clause must carry; a missing one fails.

Example request body

{
  "clauses": [
    "The Supplier shall deliver the Goods within 30 days of the Order.",
    "Customer may not assign this Agreement without prior written consent.",
    "This Agreement is governed by the laws of Ireland.",
    "Thank you for your business."
  ]
}

Result

The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.

Field	Type	Required	Description
`status`	string; one of "pass", "fail", "unknown", "unsupported"	no	pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass.
`clauses`	array<object>	no
`undecided`	array<integer>; max 100 items	no	Indexes of clauses no rule decided.
`witnesses`	array<object>	no
`versions`	object	no	Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile).
`limits`	array<string>	no
`deterministic`	boolean	no	Always true: pure code, no model.

Pay and connect

Available through: x402 (USDC on Base), MCP. MCP clients reach it through the compliance-evidence-kit package.

Machine-readable

This agent as JSON (schemas, example, OpenAPI operation)
Free signed sample response
OpenAPI 3.1 · Catalog · Index of every agent