Back to Browse
Tool Schemas - Provenance Edge Audit
x402
Tool Schemas - Provenance Edge Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.045304/call, status unknown (last checked 2026-10-16).
Binds caller-supplied implementation-manifest edges to tool-schema declarations, linking owner, revision, input/output pins, and pinned implementation artifacts for provenance tracking.
Price / call$0.045304
Success—
StatusUnknown
How this service works
Bind caller-supplied implementation-manifest edges to tool-schema declaration owner, revision, input/output pins and a pinned implementation artifact. Matching declarations do not prove deployed code conformity. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.
Output
Returns a provenance receipt confirming the binding of caller-supplied edges to tool schema declaration owners, revisions, input/output pins, and pinned implementation artifacts. Note: matching declarations do not prove deployed code conformity. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.
Example use cases
Schema revision provenance audit
“I have a list of tool schema declarations and their implementation manifests — can you bind the provenance edges between them, linking each to its owner, revision, and input/output pins? Data class is public and metadata is non-personal.”
Contract-to-artifact binding check
“We need to verify that our tool schema contracts are correctly linked to their pinned implementation artifacts — can you run a provenance edge audit on these 5 contracts and 5 implementations with dataClass set to synthetic?”
Multi-edge manifest linkage for compliance
“For our compliance review, can you bind these 10 implementation-manifest edges to our tool schema declarations, confirming the owner, revision, and pin assignments? All metadata is non-personal and the data class is public.”
Technical details
Endpoint
POSThttps://www.mahastrategies.com/api/v1/verify/tool-schemas/provenance-edge-audit?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need to formally bind and audit provenance edges between tool schema declarations and their implementation manifests, particularly when tracking owner, revision, and pin-level linkage for governance or compliance purposes. It is specifically suited for offline, typed, non-personal metadata auditing of tool schemas in public or synthetic data classes. It does not validate deployed code conformity, so pair it with runtime checks if live conformance is needed.
Side effects
- Invalid or mismatched edge/contract/implementation arrays (schema validation error)
- dataClass not set to 'public' or 'synthetic' (enum rejection)
- nonpersonalMetadata not set to true (const constraint violation)
- Array length outside 1-32 item bounds (min/max items violation)
- Declared artifact not found or unresolvable (provenance binding failure)
- Payment not processed — x402 payment required error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| edges | array | |
| contracts | array | |
| dataClass | string | |
| implementations | array | |
| nonpersonalMetadata | boolean |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"