Skip to content
vespid.ai
Quickstart

Project

This is the public project hub for vespid: one repository, one gateway model, and one reference demo that shows the full trust path over ordinary HTTP.

Featured project

vespid

A contract-first prototype for agent-native web services that keeps discovery, authorization, approval, artifacts, and audit evidence inside the same HTTP runtime story.

contract-first HTTP runtime task resume
Documentation

Understand the model

Use the docs for the gateway rules, contract semantics, and quickstart flow behind the prototype.
Blog

Read the rationale

Use the blog for the architectural decisions that explain why the project stays HTTP-first and contract-first.
1 public prototype The site, repository, docs, and blog now all point to vespid instead of splitting across unrelated public stories.
1 reference service The current demo service is appointment booking, used to prove grant, approval, resume, artifact, and audit behavior.
1 gateway runtime The supported v0.1 path is generic HTTP through the local gateway runtime, not a special client or adapter product surface.
What the current prototype covers

The current vespid execution model

vespid is not trying to be a complete agent platform yet. The current slice is narrow on purpose: make one service contract legible, route execution through one gateway, and prove the highest-value trust transitions end to end.

Discover
Live

Load service capabilities

The gateway discovers a service from /.well-known/agent-service.json and derives capabilities from the OpenAPI agent extensions.

Authorize
Live

Issue scoped grants

Consequential actions require a temporary grant that matches the capability and task binding instead of an unbounded session shortcut.

Approve
Live

Resume the original task

After grant issuance, the gateway resumes the original task and waits for approval instead of creating a duplicate consequential task.

Audit
Live

Persist artifacts and evidence

The runtime stores artifacts and audit events so the whole path can be inspected after execution, not merely observed in logs.

Suggested path
Start with the project page

Open vespid first for the clearest summary of scope, trust boundary, and public entry points.

Then read the docs

Use Documentation for the contract and runtime model that should stay stable after launch notes fade.

Then read the rationale

Use Blog when you want the reasoning behind the HTTP-first and adapter-later posture.

Section titled “Related reading”
  • vespid: the main project page.
  • Documentation: the durable reference layer.
  • Blog: launch context and architecture rationale.