The capability layer for the agentic web.
Delphy makes businesses, APIs, services, workflows, MCP servers, and skills discoverable to AI agents. The MVP is an agent-readable registry shell centered on validated delphy.json profiles and Skill Pack URLs such as /skill.md.
$ delphy registry search capability-layer
> mode: public discovery
> surfaces: web | json | skill.md
> bridge: Web/API now, MCP later
> runtime: not enabled in v0.1
A small registry before a runtime.
- 1Describe a business, API, service, workflow, or skill in a structured capability profile.
- 2Validate the profile as delphy.json so agents can understand required context and boundaries.
- 3Publish public web, Markdown, and JSON surfaces that agents can read without installing MCP.
Agent-readable from the start.
A Delphy profile explains what a capability can do, what input an agent should collect, what requires human approval, and which integration paths are available. This shell has no execution/runtime/payment/booking behavior: it does not execute actions, book services, take payments, or host MCP tools.
{
"id": "example-service",
"name": "Example Service",
"summary": "Explains how agents can discover a capability.",
"capabilities": [
{
"id": "answer_questions",
"description": "Answer questions about supported services.",
"humanApprovalRequired": false
}
],
"agentInstructions": "Search first, read the profile, then ask for missing context."
}Web/API now, MCP later.
The public MVP should let a normal chat user paste a Delphy URL into an agent. After the public web and JSON API contracts are stable, MCP can wrap the same registry for developers and power users.
/skill.md/search?q=.../c/:slug/delphy.json/api/search