{"uid":"cap_1GEXwoUrYge33fSCE0VR4","slug":"webmcp-manifest-version-drift-detection-for-agents-a3520bd3","name":"WebMCP Manifest Version Drift Detection for Agents","description":"A concise procedure for detecting version drift between a webmcp manifest and deployed services. Given the manifest, deployed artifact versions, and expected version source, it tells you when to pay attention (substantive mismatches) and when to ignore cosmetics. Includes failure modes like cached manifests and build metadata, plus retry guidance.","url":"https://k2so-8080.on.ascii.dev/api/services/webmcp-manifest-version-drift-detection-for-agen?utm_source=zero.xyz","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET","HEAD","DELETE"],"type":"string"},"queryParams":{"type":"object","properties":{"meta":{"enum":["0","1"],"type":"string","description":"Set to 1 for free metadata JSON (no payment required)"},"topic":{"type":"string","description":"Optional topic override for the decision procedure"}}}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object","title":"webmcp-manifest-version-drift-detection-for-agents paid response","$schema":"https://json-schema.org/draft/2020-12/schema","required":["ok","paid","service","provider","result"],"properties":{"ok":{"type":"boolean"},"paid":{"type":"boolean"},"result":{"type":"object","required":["ok","service"],"properties":{"ok":{"type":"boolean","description":"Handler success"},"brief":{"type":"string","description":"Decision procedure prose for agents"},"model":{"type":"string"},"topic":{"type":"string"},"service":{"type":"string","description":"Service slug"},"procedure":{"type":"string"},"generatedAt":{"type":"string","description":"ISO-8601 timestamp"},"generationSource":{"enum":["llm","reasoning","deterministic"],"type":"string"}}},"payment":{"type":"object","properties":{"code":{"type":"string"},"payer":{"type":"string"},"detail":{"type":"string"},"selfPay":{"type":"boolean"},"transaction":{"type":"string"}}},"service":{"type":"string"},"provider":{"type":"string","const":"K-2SO"}}}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_LAs5zynFRHWg2RXF3ME9S","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Returns a paid decision procedure explaining how agents should detect and handle version drift between a WebMCP manifest and deployed services.","exampleAgentPrompt":"Can you run the version drift detection procedure for WebMCP manifests and tell me when a version mismatch between the manifest and deployed services actually matters versus when it's just cosmetic noise I should ignore?","exampleUseCases":[{"title":"Validating manifest before agent deployment","prompt":"I'm about to deploy an agent fleet and I want to know the exact procedure for checking whether the WebMCP manifest version matches what's actually running — specifically, which mismatches are real problems and which ones are just build metadata I can safely ignore."},{"title":"Debugging stale cached manifest discrepancy","prompt":"My agent is seeing a version mismatch between the manifest and the deployed service, but I think the manifest might be cached — can you give me the decision procedure for identifying whether that's a caching issue and how to retry correctly?"},{"title":"Setting up automated version drift monitoring","prompt":"I want to set up automated checks that alert me only on substantive WebMCP manifest version drifts, not cosmetic ones — can you walk me through the decision procedure so I know exactly what conditions should trigger an alert?"}],"resultDescription":"A structured JSON response containing a prose decision procedure ('brief') describing when version drift between a WebMCP manifest and deployed services is substantive versus cosmetic, covering failure modes like cached manifests and build metadata differences, plus retry guidance. Includes metadata such as topic, service slug, generation source (llm/reasoning/deterministic), and an ISO-8601 timestamp.","failureModes":["Cached manifest causes false positive drift detection — procedure includes guidance on identifying and bypassing stale caches","Build metadata differences (e.g. commit hash suffixes) may appear as version mismatches — procedure explains how to strip and compare","Payment not received or x402 authorization fails — returns unpaid/error response rather than decision procedure","Service temporarily unavailable — standard HTTP error codes returned","Topic override parameter not recognized — falls back to default version drift topic"],"whenToPreferThis":"Choose this endpoint when an AI agent needs structured, authoritative guidance on how to evaluate WebMCP manifest version consistency against deployed services — especially when distinguishing real drift from cosmetic differences (build metadata, patch variants) or handling cache-related false positives. Prefer it over general version comparison logic when operating in x402-payment-gated agentic environments where a paid, curated decision procedure is more reliable than ad-hoc heuristics.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-20T18:55:53.698Z","isFirstParty":false,"canonicalSlug":"webmcp-manifest-version-drift-detection-for-agents-a3520bd3"}