Surfaced as an issue when trying to buy the obol-demo service. Tried to POST because that's what inference is. Our demo is a GET. does x402 permit or enforce verbs? assuming it allows you to gate most verbs with HTTP402, our schema and pipeline probably should handle it.
HTTP method in catalog. Two flavors: (i) doc-only — add a "common method patterns" note saying HTTP services typically GET on /, inference services POST on /v1/chat/completions. (ii) Real — add spec.upstream.method to ServiceOffer (or per-route methods), surface in services.json and the skill.md table. (i) is 5 minutes, (ii) is a CRD/schema change with tests. (i) for now and revisit when we have multi-route support, agreed?
Maybe this can just be better managed in skill docs rather than in the crd itself, tbd
Surfaced as an issue when trying to buy the obol-demo service. Tried to POST because that's what inference is. Our demo is a GET. does x402 permit or enforce verbs? assuming it allows you to gate most verbs with HTTP402, our schema and pipeline probably should handle it.
Maybe this can just be better managed in skill docs rather than in the crd itself, tbd