feat(trust): add standalone Covenant Trust service - #133
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Standalone, catalog-neutral service layer for pre-payment agent checks. Marketplaces, skill catalogs, and x402 clients stay consumers: they ask for evidence, apply their own policy, and decide whether to pay.
It returns facts rather than a universal
trusted: trueverdict:Every operation is read-only or pure cryptographic verification. The service holds no transaction signer and cannot move funds.
Interfaces: MCP over Streamable HTTP (
POST /mcp), OpenAPI (GET /openapi.json), plusGET /v1/agents/{asset},GET /v1/payment-history/{wallet},POST /v1/attestations/verify, andGET /health. The MCP surface exposes the same three checks as structured tools.Limits are documented in the README and carried in the responses rather than papered over. Transfer history covers only the reported window of PayAI fee-payer signatures, and fee sponsorship does not prove an x402 request, a settlement receipt, or job completion. A valid
covenant.attest.v1signature proves authorship by the carried key, and Covenant authorship only when that key is independently trusted.recordAuthenticcovers the validation envelope and author key only; the MIP-014 registration decode is stillnull. The v1 record list is a bounded ownership scan, so it always reportscoverage.complete: false. Registration and metadata URIs are returned but never fetched.Build is clean and all 28 tests pass.
Recreates #120 under the neutral publication identity. Branch and commit unchanged.