Expose seller response and purchase evidence - #760
Open
epistemedeus wants to merge 2 commits into
Open
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Signed-off-by: Lucian Constantinescu <epistemedeus@gmail.com>
epistemedeus
force-pushed
the
epistemedeus/response-contract-evidence
branch
from
August 12, 2026 13:19
0de506d to
9362ff4
Compare
epistemedeus
marked this pull request as ready for review
August 12, 2026 13:37
Signed-off-by: Lucian Constantinescu <epistemedeus@gmail.com>
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.
What
Expose compact seller-declared response-contract evidence on crawled OpenAPI
operations and propagate it through seller detail,
/api/route, and/api/index/tools.Each row can now report:
state:absent,partial, ordeclaredsource: seller_openapiruntimeVerified: falseWhy
An x402 route can be discoverable and payable while its OpenAPI contract does
not guarantee the output a buyer needs. A concrete example is Zerion's paid
transaction-simulation POST: the success schema requires
data, but onlydescribes nested
data.attributes.This change gives routing clients the evidence needed to filter or perform
their own authorization. It deliberately does not change Agent402's ranking,
payability, or execution behavior.
Safety boundaries
partialinstead of failing the seller crawlagent-payment-policy@0.11.1Verification
node scripts/test-openapi-fallback.jsTARGET_URL=http://127.0.0.1:3210 node scripts/test-projection-parity.jsnpm testnpm audit --omit=devThe focused suite covers multi-variant intersection, described-but-optional
nested fields, unresolved schemas, malformed schemas, Bazaar merge retention,
and three-surface projection parity. The normal unit suite and dependency audit
pass under the repository's required Node 22.22.2 runtime.
On Agent402's current 533-operation, 1.15-MB OpenAPI, normalization measured
about 7 ms median and 10.9 ms p90 locally. Compact internal storage reduced the
projected 77,689-tool cache overhead from about 12.5 MB to 3.1 MB while every
buyer-facing surface keeps the readable object.
Related seller finding: zeriontech/zerion-ai#111
Purchase-evidence follow-up
The same reporting-only path now recognizes the neutral pre-purchase evidence profile from
agent-payment-policy@0.12.0. The crawler reads the boundedLinkheader from seller discovery responses, requires registereddescribedbyplus the exact absolute extension relation, fetches at most one same-origin manifest per seller with redirects disabled, and cross-checks exact GET/POST operations against the current OpenAPI schema digest and complete guaranteed-path set.The seller-level projection retains the public manifest identity once. Compatible route projections carry only a compact
seller_manifestmarker. Missing or invalid evidence does not affect ranking, health, routing, authorization, or payment. No per-route probe was added.This follows a deterministic external screen where twelve live-valid Agent402 and MPP routes exposed zero compatible manifests. That is bounded recurrence evidence, not a prevalence claim. SameDayDesk is currently the owner-dogfood seller; merge would create a marketplace ingestion path, not independent buyer demand or certification.
Local acceptance: focused OpenAPI fallback and ingestion suite, 59/59 core checks, security regressions, package-integrity 27/27, live projection parity 21/21, and zero production dependency findings.