qub for developers
qub for developers
The HTTP API is versioned under /api/v1; its OpenAPI document currently reports API version 1.0.0. Three integration paths are supported:
- HTTP API — the complete external surface is generated from operations marked
x-audience: externalin /api/v1/openapi.json. Public operations need no credentials; browser writes use Cloudflare Turnstile; Builder calls useAuthorization: Bearer qub_sk_…./api/v1/uploadaccepts locally sealed bytes, while/api/v1/sealis an explicitly trusted server-side plaintext path. - MCP server —
tools/qub-mcpis a local Rust binary with five tools:create_qub,read_qub,check_status,list_pending_operationsandverify_forecast_series. It seals locally. Qubs are private by default (wrapped, with the key in the link fragment);visibility: "public"is an explicit opt-in that keeps the time lock and drops the link gate. Publishing is disabled by default;create_qubrequires bothQUB_API_KEYandQUB_MCP_ALLOW_CREATE=true. Reads take a delivery URL ortx_id, and needkey_base64urlonly for private qubs. - Embed —
<qub-embed src="https://qub.social/c/<tx_id>#<key>">renders the live countdown and reveal inline. Public qubs use the samesrcform without a fragment. Use the pinned loader/embed/v1.js;/embed.jsis only the moving alias.
Portable .qub bundles verify content integrity, drand-round binding, and signatures offline with qub-verify. That does not show when a qub was sealed. For public qubs, qub-verify --timing and the MCP read tools report the block time of the qub’s permanent-storage transaction as agreed by gateways that qub does not run; timing evidence is not offered for private qubs in this release.
A free Builder trial (10 publications and 10,000 authenticated reads in total; upload and read only) is offered on this page when enrolment is open. It may not be open.
See llms.txt for the agent-oriented summary, llms-full.txt for the concatenated documentation bundle, and the rendered OpenAPI reference for schemas and responses.