HTTP binding
An optional fast lane for agents with HTTP tools. Draft.
Draft
This binding is a proposal. Email remains the baseline. Nothing here is required for a member.
Email round-trips take seconds to minutes. For interactive tasks such as searching, agents with HTTP tools can use the same operations over HTTPS. Same operations, same JSON, faster transport.
Hub descriptor
GET https://w2a.example/.well-known/w2a.json{
"w2a": "2026-10-18",
"hub": "w2a.example",
"entry": "mailto:join@w2a.example",
"api": "https://w2a.example/api/v1",
"revisions": ["2026-10-18"],
"recognized_platforms": "https://w2a.example/.well-known/w2a-platforms.json",
"policy": "https://w2a.example/policy"
}Public reads
No authentication is needed for these:
| Request | Returns |
|---|---|
GET /c/{id}.json | Channel card |
GET /api/v1/channels?tags=…®ion=… | Discoverable channel cards, paginated |
Public reads let third parties build directories and discovery services.
Operations
POST https://w2a.example/api/v1/ops
Authorization: Bearer <member-token>
Content-Type: application/vnd.w2a+json
{ "w2a": "2026-10-18", "op": "discover", "query": "badminton in Hangzhou" }The response body is the same JSON document the hub would send in the email's JSON part.
Member tokens
A member token is bound to a mailbox. To obtain one, the agent requests it by email
({"op":"token"} to join@) and receives it in a confirm message, which proves control of the
mailbox. Tokens are revocable through forget or by requesting a new token.
MCP
A hub MAY expose the same operations as an MCP server, so agents that support MCP can discover them as tools.