Revision Lineage Check
0.006 USDCReleased contract
Listed in Bazaar merchant record
Checks whether a declared revision transition is consistent with its stated predecessor.
Details and limitations
Check a revision handoff before reusing evidence. Compare one initial or superseding transition with its declared predecessor; return lineage inconsistencies and an integrity receipt. Does not establish authenticity, semantic equivalence or inherited review approval.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Check one initial or superseding revision transition against a declared predecessor. Returns lineage inconsistencies and an integrity receipt. Does not establish authenticity, semantic equivalence or inherited review approval.
POST /api/v1/micro/revision-lineage-check
Exact amount: 6000 USDC base units
- Recorded successful calls
- 3
- Unpaid 402 challenges
- 10396
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
3 attributed transfers (1 external, 2 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Evidence-Frame Compatibility Check
0.0105 USDCReleased contract
Listed in Bazaar merchant record
Flags unsupported relationships or missing information in declared claim-evidence pairs using versioned rules.
Details and limitations
Check up to ten declared claim-evidence relationships against a finite, versioned rule set. Reports unsupported frame transfers and missing information. Unknown combinations remain unresolved. No prose interpretation, source inspection or truth certification.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Check up to ten declared claim-evidence relationships against a finite, versioned rule set. Reports unsupported frame transfers and missing information. Unknown combinations remain unresolved. No prose interpretation, source inspection or truth certification.
POST /api/v1/micro/evidence-frame-compatibility
Exact amount: 10500 USDC base units
- Recorded successful calls
- 2
- Unpaid 402 challenges
- 9030
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
2 attributed transfers (1 external, 1 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Bounded MCP Tool Contract Compatibility
0.015 USDCReleased contract
Listed in Bazaar merchant record
Compares declared MCP tool names, schema hashes, protocol version and transport without contacting the server.
Details and limitations
Check declared MCP tool contracts before an upgrade. Compare required names and exact input/output schema digests with a supplied server snapshot, protocol version and transport. No server contact, semantic schema-subtyping proof or official conformance certification.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare required tool names and exact pinned input/output schema digests against a declared MCP server snapshot. Checks protocol version and transport. Not a network probe, general schema-subtyping proof or official conformance certificate.
POST /api/v1/micro/mcp-contract-compatibility
Exact amount: 15000 USDC base units
- Recorded successful calls
- 3
- Unpaid 402 challenges
- 9124
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
3 attributed transfers (2 external, 1 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Citation Binding Check
0.016 USDCReleased contract
Listed in Bazaar merchant record
Flags mismatches in declared citation identities, revisions and locators, without fetching or judging the sources.
Details and limitations
Check citation metadata before an evidence review. Compare up to 20 declared source identities, revisions and locators; return exact mismatches and an integrity receipt. No source retrieval, passage-existence check or claim-support verification.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare up to 20 declared source identities, revisions and locators. Returns exact mismatches and an integrity receipt. Does not fetch sources, establish passage existence or verify claim support.
POST /api/v1/micro/citation-binding-check
Exact amount: 16000 USDC base units
- Recorded successful calls
- 3
- Unpaid 402 challenges
- 10451
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
3 attributed transfers (1 external, 2 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Structured Policy-Version Comparison
0.017 USDCReleased contract
Listed in Bazaar merchant record
Compares two structured policy versions and lists added, removed or changed clauses and scopes.
Details and limitations
Review a structured policy revision before release. Compare up to 40 caller-supplied clauses per version by stable ID, text and scope; report additions, removals and changes. Checks declared chronology, not legal effect, applicability or compliance.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare up to 40 caller-supplied policy clauses per version by stable ID, text and scope. Reports added, removed and changed clauses. Checks declared chronology, not legal effect, applicability or compliance.
POST /api/v1/micro/policy-version-comparison
Exact amount: 17000 USDC base units
- Recorded successful calls
- 2
- Unpaid 402 challenges
- 9085
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
2 attributed transfers (1 external, 1 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Audit Export Normalizer
0.018 USDCReleased contract
Listed in Bazaar merchant record
Normalizes audit-event metadata and rejects duplicate IDs, malformed timestamps and invalid digests.
Details and limitations
Prepare an audit-event export for deterministic comparison. Normalize up to 100 metadata events and reject duplicate IDs, malformed times or digests. Does not prove events occurred or establish provenance or completeness against an external system.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Normalize up to 100 metadata events into deterministic order, rejecting duplicate identifiers and malformed times or digests. Does not prove event occurrence, provenance or completeness against an external system.
POST /api/v1/micro/audit-export-normalizer
Exact amount: 18000 USDC base units
- Recorded successful calls
- 3
- Unpaid 402 challenges
- 10463
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
3 attributed transfers (1 external, 2 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Declared Control-Evidence Gap Check
0.019 USDCReleased contract
Listed in Bazaar merchant record
Flags missing or stale declared evidence against control requirements, without certifying compliance.
Details and limitations
Find missing or stale declared evidence before a governance review. Compare up to 40 control requirements with revision- and scope-bound evidence descriptors. Does not inspect evidence contents, evaluate control effectiveness or certify compliance.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare up to 40 declared policy/control requirements with revision- and scope-bound evidence descriptors. Reports missing, stale and rejected evidence. Does not inspect evidence content, evaluate control effectiveness or certify compliance.
POST /api/v1/micro/control-evidence-gaps
Exact amount: 19000 USDC base units
- Recorded successful calls
- 2
- Unpaid 402 challenges
- 9109
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
2 attributed transfers (1 external, 1 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Tool Permission Change Analysis
0.021 USDCReleased contract
Listed in Bazaar merchant record
Lists added and removed tool permissions, including new wildcards, between two explicit permission sets.
Details and limitations
Review permission changes before an agent release. Compare two explicit allow-only sets by tool, action and exact resource; report additions, removals and wildcard additions. Does not resolve IAM inheritance or wildcard containment, or authorize execution.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare two explicit allow-only permission sets by tool, action and exact resource identifier. Reports additions, removals and wildcard additions. Does not resolve IAM inheritance, wildcard containment or authorize execution.
POST /api/v1/micro/tool-permission-diff
Exact amount: 21000 USDC base units
- Recorded successful calls
- 2
- Unpaid 402 challenges
- 9095
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
2 attributed transfers (1 external, 1 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Publication Bundle Consistency
0.022 USDCReleased contract
Listed in Bazaar merchant record
Checks declared article, registry and API views for inconsistent URLs, hashes, revisions and publication states.
Details and limitations
Check declared publication views before release. Compare 2-8 article, registry and API views against canonical URL, content, release and source-set digests; flag stale, withdrawn or substituted views. No live fetch, release promotion or semantic content verification.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare 2-8 declared article, registry and API views against one canonical URL, content digest, release digest and source-set digest. Reports stale, withdrawn and substituted views. No live fetch, release promotion or semantic content verification.
POST /api/v1/micro/publication-bundle-consistency
Exact amount: 22000 USDC base units
- Recorded successful calls
- 2
- Unpaid 402 challenges
- 9175
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
2 attributed transfers (1 external, 1 operator). Price matches are inference, not proof of an API call or delivery.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Evidence Conflict Comparator
0.01 USDCWithheld — not payable
Not observed in Bazaar merchant record
Highlights opposing directions among caller-labelled observations of the same claim, population and outcome.
Details and limitations
Compare 2-20 caller-labelled observations of one claim, population and outcome. Returns opposing directions and explicitly excluded observations. No literature search, source inspection, consensus judgment or factual verification.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Compare 2-20 caller-labelled observations of one claim, population and outcome. Returns opposing directions and explicitly excluded observations. No literature search, source inspection, consensus judgment or factual verification.
POST /api/v1/micro/evidence-conflict-comparator
Exact amount: 10000 USDC base units
- Recorded successful calls
- 0
- Unpaid 402 challenges
- 0
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
0 attributed transfers (0 external, 0 operator). Price matches are inference, not proof of an API call or delivery.
Outside the owner-authorized release; settlement remains disabled.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.
Release-Bound Evidence Packet
0.01 USDCWithheld — not payable
Not observed in Bazaar merchant record
Returns public source metadata tied to pinned revisions of one supported federation article.
Details and limitations
Deliver public source metadata and exact release bindings for one supported federation article at caller-pinned revisions. Uses the deployed repository snapshot, not a live registry probe. No private review material, full source text or expert certification.
- Public or synthetic inputs only. Caller labels are declarations, not independently verified facts.
- No source acquisition, model inference, expert review, regulatory certification or prediction is performed.
- Receipt hashes bind the supplied input, version and result. They are not signatures, trusted timestamps, anonymization or proof of truth.
- Request and result bodies and their digests are not persisted by this service. Payment metadata remains in the existing settlement ledger.
- Stateless delivery: save the response locally. A lost response is not recoverable from a stored job. Do not sign a new payment after an ambiguous outcome without checking settlement.
- A paid negative finding is a completed check, not approval. Malformed or unsupported inputs are refused before settlement.
- Deliver public source metadata and exact release bindings for one supported federation article at caller-pinned revisions. Uses the deployed repository snapshot, not a live registry probe. No private review material, full source text or expert certification.
POST /api/v1/micro/release-bound-evidence-packet
Exact amount: 10000 USDC base units
- Recorded successful calls
- 0
- Unpaid 402 challenges
- 0
- Declared operator calls
- 0
- Recorded unsuccessful calls
- 0
0 attributed transfers (0 external, 0 operator). Price matches are inference, not proof of an API call or delivery.
Outside the owner-authorized release; settlement remains disabled.
Inspect contract in OpenAPI ↗Free example and contract ↗This service does not persist request/result bodies or their digests. No stored-result recovery. Payment binds the resource; the integrity receipt binds the actual input. Do not send confidential data or place input in URLs or payment metadata.