Start with an invitation
Blockquote is coming soon. Join the waitlist for launch updates. Invited collaborators join a site through an email invitation. Use the invited email address to create an account, verify it, sign in, and accept the invitation. Site creation is restricted to the platform owner during this phase.
Administrators can invite collaborators, change roles, and revoke access. An editor can work on drafts once content editing ships; a publisher will also have publication permission. Removing membership stops access to that site on subsequent requests.
Current API conventions
The foundation API uses versioned administration routes under /v1 and authentication endpoints under /api/auth. Browser administration uses verified sessions and trusted-origin checks. It is not yet a machine-token content API.
| Endpoint | Purpose |
|---|---|
GET /v1/me | Current verified user and site-creation permission |
GET /v1/sites | Sites the current user belongs to |
GET /v1/sites/:id/members | Site members, available to administrators |
POST /v1/sites/:id/invitations | Invite a collaborator with an explicit role |
POST /v1/invitations/accept | Accept a single-use invitation as its verified recipient |
Planned website integration
The content milestone will add versioned schemas, drafts, immutable publication, and delivery queries. The planned TypeScript SDK will expose typed published content. The Next.js example will demonstrate rendering, preview, and revalidation after publication.
Portable Text is the intended rich-text contract. Page sections will have schema-defined fields and component identifiers. Your website will supply the matching frontend components. These interfaces are not released yet; there is no SDK installation command or live MCP endpoint to connect to today.
Planned agent integration
The MCP interface is intended to support schema discovery, declarative schema changes, resumable site setup, content drafts, asset uploads, and explicit publishing. OAuth authorization will grant access to particular sites and capabilities.
Begin with the MCP site-setup guide for the intended workflow. This documentation will gain versioned tool contracts and runnable examples as those interfaces become available.
Formats and localization
Read the Portable Text guide for the rich-content contract and the localization guide for draft, publication, and fallback decisions. Locale configuration is implemented; translated documents and locale-aware delivery are still upcoming.
Current product status is the reference for what has shipped. Questions about testing an integration can go to hello@blockquote.com.