Give your agents a durable place to work.

Ask, search, write, retain files, sync Markdown, and test through resources that return durable receipts.

POST /v1/questionsProduction
curl https://api.corvio.ai/v1/questions \
  -H "Authorization: Bearer $CORVIO_API_KEY" \
  -H "Idempotency-Key: launch-risk-review" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "What launch risks remain?",
    "sources": ["workspace", "memory"]
  }'
201 CREATEDquestion_idconversation_idsource_document_ids

Useful work leaves evidence.

Corvio responses are designed for iteration. Follow returned links and IDs instead of reconstructing state from prose.

Durable by default

Answers return stable question, conversation, document, source, and artifact IDs.

Authority rechecked

Every call re-evaluates the key owner, Workspace membership, role, scope, ACL, expiry, and revocation.

Safe to retry

Creates accept Idempotency-Key; document replacement accepts an expected content revision.

A question is a resource, not a disposable response.
{
  "id": "question_uuid",
  "status": "completed",
  "conversation_id": "conversation_uuid",
  "source_document_ids": ["document_uuid"],
  "artifacts": [{
    "kind": "document",
    "document_id": "artifact_uuid",
    "content_revision": 4
  }],
  "links": {
    "self": "/v1/questions/question_uuid",
    "conversation": "/v1/conversations/conversation_uuid"
  }
}

Small enough to learn. Complete enough to operate.

The generated reference remains the exact operation authority; this map shows the durable capability boundaries.

Questions

Ask Corvio, inspect durable runs, and continue with conversation_id.

GET · POST/questions

Conversations

Recover stable continuation handles without replaying chat history.

GET/conversations

Workspace search

Search knowledge with page, node, chunk, and source references intact.

POST/search

Documents

List, read, create, revision-update, archive, and privately share documents. Projects stay at the Workspace root; deeper structures use branch Pages and leaves.

GET · POST · PUT · DELETE/documents

Workspace files

Retain originals, read bounded hash-bound source projections, download exact bytes, and launch organization runs with stable Asset handles.

GET · POST/files

Local Markdown sync

Plan, pull, push, commit, and explicitly resolve revision/hash conflicts.

GET · POST/sync

Test control

Discover catalog contracts and launch Workspace-bound test runs as an administrator.

GET · POST/admin/tests

Install the operating model, not another prompt snippet.

corvio-operate-workspace tells an Agent it must make one authorized Corvio read before research, reports, comparisons, plans, decisions, meeting notes, project work, debugging, reviews, or follow-ups. It complements the host's normal file workflow and preserves only results worth sharing or revisiting. Exact continuation handles keep the prior subject authoritative: the Agent reads that owner before broad search and treats lexical matches elsewhere as candidates, not replacement context. A handle identifies subject evidence, not necessarily the durable write destination; when a repeated pattern, preference, constraint, quality bar, or method should be reused later, the Agent searches narrowly in the same Project or Workspace for the fitting Memory or Skill owner before admitting or merging it. When people ask where to continue, it returns a compact current map of the canonical owner, next-useful leaves, relevant reusable Skill, revisions, and unresolved checkpoint instead of dumping the whole Project. Copyright, public availability, or third-party authorship alone does not make a selected source restricted; applicable terms that forbid private Workspace retention or processing still do. Credentials, regulated or privileged data, genuinely disclosure-unclear sources, and explicitly local-only work remain outside Corvio. Private or confidential material selected for authorized private Workspace use instead retains strict owner, ACL, and cross-scope reuse boundaries. A one-off result is normally a no-write boundary, not a reason to skip relevant prior work.

Example agent request

Use $corvio-operate-workspace to find the latest launch plan, summarize unresolved risks with source document IDs, then continue that Corvio conversation and create a prioritized checklist.

Discovery → evidence → durable effect → verification

Build with the same contracts Corvio uses to verify itself.