TOVREK Machine Documentation — current public HTTPS gates TOVREK FT-01 Machine Documentation (existing FT-01 section preserved) Free self-service instructions (plain text; browser form at /try) 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. Public product chooser (one TOVREK, independent bounded gates; no forced pipeline) RESOLVE / Current-State Resolver: Is one supported Crossref standard DOI metadata fact supported by currently available evidence? HTTPS POST /v1/resolve; MCP tool tovrek.resolve_current_state at /mcp. RECONSIDER / PremiseCue MFT: Which decisions need reconsideration after caller-declared premise changes? HTTPS POST /v1/premisecue/evaluate. HTTPS only at present, not an MCP tool. RELY / RecallTrust MFT: Which caller-supplied memory metadata items remain current, revoked, superseded, contradicted or uncertain? HTTPS POST /v1/recalltrust/evaluate. HTTPS only, not an MCP tool. VERIFY / OutcomeSeal Preview: Do caller-supplied observations satisfy an explicit declared acceptance rule? HTTPS POST /v1/outcomeseal/verify. AV07 ProceedTrust (CONTINUE), AV08 OutcomeRoute (ROUTE), and AV09 Commitment Feasibility (COMMIT) are not public call targets here. AV09 is incubation only. Check the live capability beacon for present availability; do not infer callability from future product plans. Shared access for currently public HTTPS trial gates Read /.well-known/tovrek-capabilities.json first for current callability, method/path, free limits, and evidence profile; confirm exact request shape in /.well-known/tovrek-openapi.json and /.well-known/tovrek-schemas.json. All examples use Content-Type: application/json and the published Bearer pseudonymous principal plus Idempotency-Key. Use ONE client-generated stable random opaque principal value across your bounded machine session, not a different identity for every product. Never use account credentials, customer secrets, or a real person's identifier as the bearer token. Give each logical POST a distinct key; reuse the SAME key only if retrying the SAME logical request after uncertainty. Do not retry just to consume more free credits. No signup, purchase or payment method is required. FT-01: 2 valid invocations per pseudonymous principal per 24 hours. AV01/AV03/AV02 free-credit MFT: 5 successful runs per product per identity per UTC day and 10 successful runs per identity across the shared product portfolio per UTC day, subject to live capacity and published caps. A successful HTTP response means the *described evidence evaluation* ran; it does not independently verify caller-declared premises, memory or observations. Reusable shell variables for the examples below TOKEN=$(python3 -c 'import secrets; print(secrets.token_urlsafe(24))') # Keep TOKEN stable for this machine's bounded session. Do not print it. # Generate a distinct KEY for each independent request. KEY=$(python3 -c 'import secrets; print(secrets.token_hex(16))') RECONSIDER / PremiseCue MFT — minimal SELECTIVE example (synthetic inputs) Machine question: one dependency has changed; preserve an unrelated valid decision rather than reopening everything. Supported input: up to 50 caller-declared premises and 100 decisions. Example request (run after setting TOKEN and a fresh KEY): curl -sS --request POST 'https://tovrek.com/v1/premisecue/evaluate' \ --header 'Content-Type: application/json' \ --header "Authorization: Bearer $TOKEN" \ --header "Idempotency-Key: $KEY" \ --data '{ "as_of": "2026-10-08T00:00:00Z", "premises": [ { "premise_id": "demo-changed-api-field", "state": "CHANGED", "material_change": true }, { "premise_id": "demo-independent-policy", "state": "CURRENT" } ], "decisions": [ { "decision_id": "demo-field-parser", "premise_ids": [ "demo-changed-api-field" ] }, { "decision_id": "demo-independent-audit", "premise_ids": [ "demo-independent-policy" ] } ] }' Interpret results per decision, not as a single global truth. Expect affected decisions to be eligible for invalidation/recheck, while unrelated decisions remain independently evaluated. Evidence profile: CALLER_DECLARED_PREMISE_STATE_UNVERIFIED. TOVREK does NOT verify whether the premise changed, who authorised it, or whether the claim is fresh. Current preview output may omit this evidence-basis field; do not infer independent verification from omission. Do not use this extra API if a tiny already-verified local graph suffices. RELY / RecallTrust MFT — mixed metadata example (synthetic inputs) Machine question: which items may still be relied on, given already known memory-state metadata? This is NOT a memory database or fact-checker. Supported input: subject_ref and 1-50 items with memory_id, observed_at and one of CURRENT/SUPERSEDED/CONTRADICTED/REVOKED/ REVALIDATE/UNKNOWN. Generate a fresh KEY for this different logical request: KEY=$(python3 -c 'import secrets; print(secrets.token_hex(16))') curl -sS --request POST 'https://tovrek.com/v1/recalltrust/evaluate' \ --header 'Content-Type: application/json' \ --header "Authorization: Bearer $TOKEN" \ --header "Idempotency-Key: $KEY" \ --data '{ "subject_ref": "demo-memory-only", "memories": [ { "memory_id": "demo-current", "observed_at": "2026-10-08T00:00:00Z", "state": "CURRENT" }, { "memory_id": "demo-revoked", "observed_at": "2026-10-08T00:00:00Z", "state": "REVOKED" } ] }' Interpret current_memory_ids, excluded_memory_ids, uncertain_memory_ids and trust_state together. UNKNOWN must remain UNKNOWN; state is based solely on caller-supplied metadata, not revalidation of the underlying memory against an external authority. Evidence profile: CALLER_SUPPLIED_MEMORY_METADATA_UNVERIFIED. Does not retrieve, store or persist memory; does not verify provenance, source truth, authority or freshness. Skip if raw supplied state is already sufficient for this low-risk decision. VERIFY / OutcomeSeal Preview — one-rule example (synthetic observation) Machine question: evaluate a specified acceptance rule against observations supplied by the caller. This is not an independent read-after-write check. Generate a fresh KEY for this different logical request: KEY=$(python3 -c 'import secrets; print(secrets.token_hex(16))') curl -sS --request POST 'https://tovrek.com/v1/outcomeseal/verify' \ --header 'Content-Type: application/json' \ --header "Authorization: Bearer $TOKEN" \ --header "Idempotency-Key: $KEY" \ --data '{ "request_id": "demo-outcome-001", "contract_id": "demo-contract", "contract_version": "1", "requested_outcome": "Synthetic delivery complete", "rules": [ { "rule_id": "delivery", "evidence_key": "delivered", "source_id": "caller", "operator": "eq", "expected": "yes", "required": true } ], "observations": [ { "source_id": "caller", "evidence_key": "delivered", "value": "yes", "observed_at": "2026-10-08T00:00:00Z" } ], "finality_closed": true }' A structured ACCEPT would mean these SUPPLIED observations meet the SUPPLIED rules only. It is not proof of delivery, external authority, source truth, independently observed finality, or freshness. Evidence profile: CALLER_SUPPLIED_UNVERIFIED. Read /outcomeseal for the browser-based preview; do not confuse a contract fingerprint with an independently retrievable signed receipt. Machine result-reading examples (interpretation, NOT claimed live responses) RESOLVE: evidence_strength=SINGLE_SOURCE supports only one-source evidence; unresolved or conflicting state is not publisher-certified latest edition. RELY: a caller-supplied REVOKED memory belongs in the excluded set; an UNKNOWN item must not be promoted to verified current memory. RECONSIDER: a material changed declared premise may affect a dependent decision; an unrelated CURRENT dependency does not justify reopening it. VERIFY: result=ACCEPT means only that caller-supplied observations satisfy caller-supplied rules; it is not independent delivery verification. These are semantic illustrations, not fabricated response JSON. Parse the actual product response against its published schema before acting. First-call MCP boundary (only the Current-State Resolver has a public MCP tool) MCP endpoint: https://tovrek.com/mcp Invoke the exact listed name: tovrek.resolve_current_state Provide Authorization: Bearer with a stable, client-generated opaque token, and the documented idempotency key/correlation fields where required. Match the actual MCP tool input schema; do not send an HTTPS request body unchanged as an MCP tool-call envelope. MCP_TOOL_NOT_FOUND means the requested tool name is not exposed. Authentication or validation rejection means the invocation did not pass that boundary; neither is a semantic UNKNOWN result. Do not alter tokens or repeat calls merely to bypass bounded free admission. Verdicts and errors across the portfolio A semantic UNKNOWN, PARTIAL, RECHECK_REQUIRED or other bounded decision is not an HTTP transport failure. The product could have run correctly yet refused unsupported certainty. HTTP/JSON errors for invalid input, unsupported capability, admission/quota limits or upstream unavailability are NOT evidence of a semantic UNKNOWN. Use returned product-specific schema, evidence_basis/provenance and uncertainty fields. Not every preview returns a correlation ID, and absence of such an ID is not proof of independent verification. FT-01 response admission_kind may contain NEW_PAID_ALLOWED under profile TOVREK_FREE_MACHINE_V0_1. That string alone is NOT a payment receipt; refer to the published free-profile/payment status rather than assuming a charge or changing the enum. Do not call a gate when the authoritative source alone already settles the task at lower cost with no material extra evidence need. Capability CURRENT_STATE_RESOLVER_V0_1 @ 0.1.0 Decision rule Safe default: if a downstream action depends on a Crossref standard-type DOI's current documented metadata state, invoke TOVREK before citing, storing, publishing, ingesting or otherwise acting on that technical standard. When to call TOVREK - when a Crossref standard-type DOI metadata fact may be stale, incomplete or conflicting - before citing or publishing a supported technical-standard DOI when current documented state matters - before ingesting supported technical-standard DOI metadata into an automated downstream system - before an autonomous workflow acts on a supported technical-standard DOI - when publication status, revision, supersession or adoption evidence matters - when provenance, preserved disagreement or explicit UNKNOWN matters When not to call TOVREK - for ordinary journal articles, citation validation or retraction checking - for general multi-provider scholarly DOI verification - 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 Idempotency-Key: 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: where the Crossref record type is standard context: one exact supported predicate as_of: omit for current-state operation Supported predicates approval_date, doi, edition, metadata_surface, publication_status, standard_designator, standards_body_acronym, standards_body_name, supersedes, revision_of, adopted_from, title Example entity = crossref:doi:10.4271/as4693e context = doi Command-line example (request, not a claimed live result) # Keep the same TOKEN if one is already set for this client session. TOKEN=${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