ObolNetwork / ObolNetwork/obol-stack
`sell` CRDs may not specify a HTTP VERB. Are we selling GETs? POSTs? etc.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the CRD/schema, services.json, and skill.md, then compare the proposed documentation-only approach with adding an upstream method to ServiceOffer. Done means the chosen approach clearly explains or represents HTTP methods, with tests included if the CRD/schema path is selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100