Support
vespid is public and experimental. Support is most useful when it helps turn questions about agent-native services into better contracts, clearer runtime semantics, and more reproducible demos.
Open an issue when you want to propose
Section titled “Open an issue when you want to propose”Open an issue in vespid-ai/vespid when you want to propose:
- a contract field or
x-agent-*semantic that is missing or underspecified - a new fail-closed or task-resume test case
- a better reference service beyond the current appointment demo
- documentation that would make the gateway model clearer
- a future adapter direction that can be justified from the canonical HTTP contract
What to include
Section titled “What to include”The most useful issues include:
- the problem statement in one sentence
- the service or capability surface involved
- whether the issue is about discovery, authorization, approval, execution, artifacts, or audit
- a minimal reproduction path or expected HTTP flow
- what success would look like in code, docs, or tests
When to use the docs first
Section titled “When to use the docs first”Before opening a broad issue, it is usually worth checking:
That keeps the conversation grounded in the current public scope instead of asking the repo to become a vague “agent platform.”
Public links
Section titled “Public links”- the repo: https://github.com/vespid-ai/vespid
- issues: https://github.com/vespid-ai/vespid/issues
- the docs hub: https://vespid.ai/docs/
- the website: https://vespid.ai/
That keeps support grounded in real public surfaces instead of off-platform context.