run402-mcp
Version:
MCP server for Run402 — full-stack backend infrastructure for AI agents: Postgres, auth, storage, serverless functions and atomic deploys. Paid with x402/MPP. Includes $0.03 image generation.
27 lines • 1.32 kB
JavaScript
/**
* Request/response types for the `rooms` namespace — agent-messaging
* coordination rooms (`/orgs/v1/:org_id/rooms/:room_key/*`): session-grained
* presences, room-visible addressed messages, and TTL-expiring advisory
* claims.
*
* Rooms are org-scoped and auto-vivify on first use (there is no create
* call). A room key equal to a project id is that project's DEFAULT room —
* the zero-config rendezvous for agents sharing a `run402.config.json`.
* Load-bearing conventions:
*
* - **Presence names are unique per room, forever** (never recycled). A
* `requestedName` is honored verbatim when free, else deterministically
* suffixed (`Opus` → `Opus-2`) with the registration reporting
* `renamed: true` — never an error, never a retry.
* - **Claims are advisory and never block** anything, anywhere (deploys
* included): claim creation always succeeds and reports the complete
* `conflicts[]`.
* - **Message cursors are OPAQUE** (`mcr_…`): store the page's `cursor` and
* echo it back next time — never parse one. An unusable cursor never
* errors; the page returns `reset: true` + `earliest_cursor`.
*
* Every response interface carries an index signature so additive gateway
* fields pass through untyped.
*/
export {};
//# sourceMappingURL=rooms.types.js.map