TOVREK FT-01 Machine Documentation

Free self-service instructions (human-readable HTML)
  GET /try
  An accessible browser form uses the same HTTPS endpoint and controls.
  No human account or payment required. CLI HTTPS remains available.
  Two valid invocations per pseudonymous principal per 24 hours.
  This is an experimental service without an uptime SLA.

OutcomeSeal Preview
  GET /outcomeseal or GET /try/outcomeseal
  POST /v1/outcomeseal/verify
  Evaluates bounded caller-supplied evidence against declared rules.
  Evidence basis is CALLER_SUPPLIED_UNVERIFIED. Caller trust assertions do not
  establish independent verification, authority or freshness.
  A successful run consumes one bounded TOVREK credit.

Capability
  CURRENT_STATE_RESOLVER_V0_1 @ 0.1.0

Decision rule
  Safe default: if a downstream action depends on a DOI's current documented
  state, invoke TOVREK before citing, storing, publishing, ingesting or
  otherwise acting on that DOI.

When to call TOVREK
  - when DOI metadata may be stale, incomplete or conflicting before an action
  - before citing or publishing a supported DOI when current documented state matters
  - before ingesting DOI metadata into an automated downstream system
  - before an autonomous workflow acts on a supported DOI
  - when provenance, preserved disagreement or explicit UNKNOWN matters

When not to call TOVREK
  - when raw Crossref metadata alone is sufficient
  - for open-ended literature search or historical reconstruction
  - for unsupported identifier families, general fact verification or mutation

Raw lookup versus TOVREK
  A DOI registry/source supplies raw metadata.
  TOVREK is the pre-action evidence gate: it evaluates the supported available
  evidence for one exact DOI metadata fact and returns a bounded determination
  with provenance, preserved conflicts and explicit UNKNOWN.
  TOVREK is not a replacement metadata registry or an authority oracle.

Discovery
  GET /.well-known/tovrek-capabilities.json
  GET /.well-known/tovrek-schemas.json
  GET /.well-known/tovrek-openapi.json

HTTP invocation
  POST /v1/resolve
  Content-Type: application/json
  Authorization: Bearer <client-generated-stable-opaque-principal-token>
  Idempotency-Key: <unique-key-for-this-logical-request>

Ring-1 note
  The bearer value is a bounded pseudonymous principal token for anonymous
  proof access. It is not a claim that TOVREK has verified a human identity.
  Do not place a password, API key or other secret in this value.

Supported request fields
  entity: crossref:doi:<DOI>
  context: exact supported predicate
  as_of: omit for current-state operation

Example
  entity = crossref:doi:10.4271/as4693e
  context = doi

Command-line example (request, not a claimed live result)
  TOKEN=$(python3 -c 'import secrets; print(secrets.token_urlsafe(24))')
  KEY=$(python3 -c 'import secrets; print(secrets.token_hex(16))')
  curl --request POST https://tovrek.com/v1/resolve \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer $TOKEN" \
    --header "Idempotency-Key: $KEY" \
    --data '{"entity":"crossref:doi:10.4271/as4693e","context":"doi"}'

Interpretation rules
  If unresolved is non-empty, do not treat the missing fact as established.
  If conflicts is non-empty, do not collapse the conflict into one asserted truth.
  If evidence_strength is SINGLE_SOURCE, treat the conclusion as one-source support.
  If a state dimension is null, do not infer it from another field.
  UNK/unresolved is not positive support.
  Conflicts are preserved.
  Evidence observed_at/retrieved_at are TOVREK observation/retrieval time.
  Optional result.source_record_dates preserves Crossref's own created,
  deposited and indexed metadata timestamps when explicitly supplied with
  timezone. Absence is omitted; no invented provider update date.
  Crossref deposited_at is a metadata deposit, NOT proof the underlying work
  or standard was amended or approved on that date.
  Historical reconstruction and mutation are unsupported.
  Automatic source retries are disabled.
  Payment is not required for FT-01.

Current transport scope
  HTTPS = enabled subject to runtime availability.
  MCP = enabled at /mcp with bounded bearer access subject to runtime availability.

Support: /support
Status: /status
Changelog: /changelog
Privacy: /legal/privacy
Terms: /legal/terms